Cyber Resilience

CVE-2026-22819

Race Condition in Outray ≤ 0.1.5

Public PoCRace Condition
Published
14 January 2026
Modified
20 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.0021 11th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2026-22819 is a medium-severity Race Condition within a Thread (CWE-366) vulnerability in Outray Outray. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Outray openSource ngrok alternative. Prior to 0.1.5, this vulnerability allows a user i.e a free plan user to get more than the desired subdomains due to lack of db transaction lock mechanisms in main/apps/web/src/routes/api/$orgSlug/subdomains/index.ts. This vulnerability is fixed in 0.1.5.

CWE(s)
CWE-366

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22820Same product: Outray Outray
CVE-2023-3218Shared CWE-366
CVE-2025-58143Shared CWE-366
CVE-2024-10630Shared CWE-366
CVE-2026-3904Shared CWE-366
CVE-2026-46181Shared CWE-366
CVE-2023-4127Shared CWE-366
CVE-2023-6546Shared CWE-366
CVE-2026-23684Shared CWE-366
CVE-2024-6778Shared CWE-366

Affected Assets

outray
outray
≤ 0.1.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2
  • V15.4.3
  • V17.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can include concurrency and stress testing that finds race conditions after they have been coded.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can mandate use of safe concurrency patterns that avoid introducing races.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles include requirements for synchronization primitives and thread-safe design that stop race conditions from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require synchronization primitives and concurrency analysis that prevent intra-thread race conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect race conditions through concurrency and stress testing.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes concurrency and synchronization practices that reduce race conditions.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate thread-safety and locking controls.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles address concurrent access and resource synchronization.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper synchronization primitives to prevent race conditions.

A.8.32 Change management none match
none

Change management can introduce or remove synchronization flaws during updates.

References