LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22820: Outray cli is vulnerable to race conditions in tunnels creation

Outray openSource ngrok alternative. Prior to 0.1.5, a TOCTOU race condition vulnerability allows a user to exceed the set number of active tunnels in their subscription plan. This vulnerability is fixed in 0.1.5.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22820 affects Outray, an open-source ngrok alternative. Before version 0.1.5, a timing flaw could let a user create more active tunnels than their subscription plan allows. The main business risk is quota bypass and potential service abuse, not direct data theft or system takeover based on the available sources.

Executive priority

Prioritize remediation where Outray enforces paid plans, quotas, or shared service limits. This is not currently evidenced as a takeover risk, but it can undermine billing controls and capacity management.

Technical view

Outray versions before 0.1.5 contain a CWE-367 time-of-check/time-of-use race condition in tunnel creation. The advisory states the flaw allows exceeding configured active tunnel limits. CVSS 4.0 is 6.3 with network attack vector, high attack complexity, no user interaction, and low integrity impact. Version 0.1.5 fixes the issue.

Likely exposure

Exposure is most relevant for organizations operating Outray versions below 0.1.5 with subscription plans or active tunnel quotas. The sources do not identify specific hosted services, distributions, or downstream products beyond akinloluwami/outray.

Exploitation context

The issue requires winning a race condition during tunnel creation, reflected by high attack complexity. There is no KEV listing and the provided sources do not report active exploitation or public weaponization.

Researcher notes

Public details are limited to the advisory, CVE record, and fixing commit. The vulnerability is classified as CWE-367 and impacts quota enforcement during tunnel creation. Avoid assuming broader privilege escalation or confidentiality impact beyond the stated low integrity impact.

Mitigation direction

  • Upgrade Outray to version 0.1.5 or later.
  • Review the GitHub advisory for vendor guidance.
  • Monitor active tunnel counts for quota bypass anomalies.
  • If upgrade timing is uncertain, assess temporary operational controls around tunnel creation.

Validation and detection

  • Inventory Outray deployments and identify versions below 0.1.5.
  • Confirm upgraded systems report version 0.1.5 or later.
  • Review tenant or user tunnel metrics for limit violations.
  • Check change records against the referenced fixing commit.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-367: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22820 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.3Medium
CVSS 4.0 vector shape for CVE-2026-22820Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
akinloluwamioutray< 0.1.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-367 · source CWE mapping

Time-of-check Time-of-use (TOCTOU) Race Condition

Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.