Skip to main content
CVE-2026-22819VulnerabilityPublished

CVE-2026-22819: akinloluwami outray · Race Condition within a Thread

Affects akinloluwami outraySource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.1.5 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade outray and outray-tunnel/outray to 0.1.5.

Affected software

ProductAffectedFixed in
akinloluwamioutrayAffected
  • <0.1.5
Fixed in
  • 0.1.5
GitHuboutray-tunnel/outraypkg:github/outray-tunnel/outrayOther threatsAffected
  • <0.1.5
Fixed in
  • 0.1.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade all instances of outray to version 0.1.5 or later, where the race condition has been fixed with proper database transaction locking. Organizations should audit their deployments to identify any running vulnerable versions. Additionally, implementing rate limiting and concurrency controls at the API gateway or application level can reduce the risk of race conditions. Monitoring subdomain allocation patterns for anomalies can help detect abuse attempts. For deployments where upgrading is delayed, applying manual locking mechanisms or database-level transaction isolation can serve as temporary workarounds. Security teams should also review user privilege assignments to minimize exposure and consider restricting free plan usage or enforcing stricter quotas until patches are applied.

Description

CVE-2026-22819 is a medium-severity race condition vulnerability in the open-source ngrok alternative 'outray' prior to version 0.1.5. It allows free plan users to obtain more subdomains than intended due to missing database transaction locking in the subdomain allocation code. The flaw impacts integrity and availability but does not affect confidentiality. Exploitation requires network access and low privileges but no user interaction. The vulnerability is fixed in version 0.1.5. There are no known exploits in the wild.

References

Community reviews

Loading reviews…