Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-22819 — outray

🟡 CVSS 5.9 — Medium ⚠️ Exploit Public CWE-366 OSV
5.9
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Outray has a Race Condition in the cli's webapp

Summary

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 https://github.com/akinloluwami/outray/blob/main/apps/web/src/routes/api/%24orgSlug/subdomains/index.ts

Details

  • The affected code-:

```ts

//Race condition

const [subscription] = await db

.select()

.from(subscriptions)

.where(eq(subscriptions.organizationId, organization.id));

const currentPlan = subscription?.plan || "free";

const planLimits = getPlanLimits(currentPlan as any);

const subdomainLimit = planLimits.maxSubdomains;

const existingSubdomains = await db

.select()

.from(subdomains)

.where(eq(subdomains.organizationId, organization.id));

if (existingSubdomains.length >= subdomainLimit) {

return json(

{

error: Subdomain limit reached. The ${currentPlan} plan allows ${subdomainLimit} subdomain${subdomainLimit > 1 ? "s" : ""}.,

},

{ status: 403 },

);

}

const existing = await db

.select()

.from(subdomains)

.where(eq(subdomains.subdomain, subdomain))

.limit(1);

if (existing.length > 0) {

return json({ error: "Subdomain already taken" }, { status: 409 });

}

const [newSubdomain] = await db

.insert(subdomains)

.values({

id: crypto.randomUUID(),

subdomain,

organizationId: organization.id,

userId: session.user.id,

})

.returning();

```

  • The first part of the code checks the user plan and determine his/her existing_domains without locking the transaction and allowing it to run.

```ts

const existingSubdomains = await db

.select()

.from(subdomains)

.where(eq(subdomains.organizationId, organization.id));

```

  • The other part of the code checks if the desired domain is more than the limit.

```ts

if (existingSubdomains.length >= subdomainLimit) {

return json(

{

error: Subdomain limit reached. The ${currentPlan} plan allows ${subdomainLimit} subdomain${subdomainLimit > 1 ? "s" : ""}.,

},

{ status: 403 },

);

}

```

  • Finally, it inserts the subdomain also after the whole check without locking transactions.

```ts

const [newSubdomain] = await db

.insert(subdomains)

.values({

id: crypto.randomUUID(),

subdomain,

organizationId: organization.id,

userId: session.user.id,

})

.returning();

```

  • An attacker can exploit this by making parallel requests to the same endpoint and if the second request reads row subdomains before the INSERT statement of request one is made.It allows the attacker to act on a not yet updated row which bypasses the checks and allow the attacker to get more subdomains.For example-:

```

Parallel request 1 Parallel Request 2

| |

checks for Checks the not yet updated

available subdomain row and bypasses the logic checks

and determines if it is more than limit

| |

Inserts subdomain and calls it a day Also inserts the subdomain

```

  • The attack focuses on exploiting the race window between reading and writing the db rows.

PoC

  • Intercept with Burp proxy,pass to Repeater and create multiple requests in a single batch with different subdomain names as seen below. Lastly, send the requests in parallel.

<img width="1844" height="855" alt="image" src="https://github.com/user-attachments/assets/f46d5993-31bd-4b96-902a-b2de5b0518bd" />

  • Result-:

<img width="1905" height="977" alt="image" src="https://github.com/user-attachments/assets/4c877de2-4b55-46f4-9f1c-78590dfebefc" />

Impact

The vulnerability provides an infiinite supply of domains to users bypassing the need for subscription

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-22819 is classified as CWE-366: Race Condition within a Thread. If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.

Affected software

CVE-2026-22819 is recorded against 1 package.

  • outray

Timeline and source

Published on 13 January 2026 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)

Other advisories for this package

outray has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-366: Race Condition within a Thread) in other software:

Details

Severity MEDIUM
CVSS Score 5.9
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
CWE CWE-366
Public Exploit ⚠️ Yes
Source OSV
Published 2026-01-13
Updated 2026-08-20
Modified 2026-06-17

Affected Packages

Software From version Fixed in
outray

Similar Threats

Exploit Protection

Are you running outray?

CVE-2026-22819 carries CVSS 5.9 Medium rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-22819 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026