Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-22820 — outray

🟢 CVSS 3.7 — Low ⚠️ Exploit Public CWE-367 OSV
3.7
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Outray cli is vulnerable to race conditions in tunnels creation

Summary

A TOCTOU race condition vulnerability allows a user to exceed the set number of active tunnels in their subscription plan.

Details

Affected conponent: apps/web/src/routes/api/tunnel/register.ts

  • /tunnel/register endpoint code-:

```ts

// Check if tunnel already exists in database

const [existingTunnel] = await db

.select()

.from(tunnels)

.where(eq(tunnels.url, tunnelUrl));

const isReconnection = !!existingTunnel;

console.log(

[TUNNEL LIMIT CHECK] Org: ${organizationId}, Tunnel: ${tunnelId},

);

console.log(

[TUNNEL LIMIT CHECK] Is Reconnection: ${isReconnection},

);

console.log(

[TUNNEL LIMIT CHECK] Plan: ${currentPlan}, Limit: ${tunnelLimit},

);

// Check limits only for NEW tunnels (not reconnections)

if (!isReconnection) {

// Count active tunnels from Redis SET

const activeCount = await redis.scard(setKey);

console.log(

[TUNNEL LIMIT CHECK] Active count in Redis: ${activeCount},

);

// The current tunnel is NOT yet in the online_tunnels set (added after successful registration)

// So we check if activeCount >= limit (not >)

if (activeCount >= tunnelLimit) {

console.log(

[TUNNEL LIMIT CHECK] REJECTED - ${activeCount} >= ${tunnelLimit},

);

return json(

{

error: Tunnel limit reached. The ${currentPlan} plan allows ${tunnelLimit} active tunnel${tunnelLimit > 1 ? "s" : ""}.,

},

{ status: 403 },

);

}

console.log(

[TUNNEL LIMIT CHECK] ALLOWED - ${activeCount} < ${tunnelLimit},

);

} else {

console.log([TUNNEL LIMIT CHECK] SKIPPED - Reconnection detected);

}

if (existingTunnel) {

// Tunnel with this URL already exists, update lastSeenAt

await db

.update(tunnels)

.set({ lastSeenAt: new Date() })

.where(eq(tunnels.id, existingTunnel.id));

return json({

success: true,

tunnelId: existingTunnel.id,

});

}

// Create new tunnel record

const tunnelRecord = {

id: randomUUID(),

url: tunnelUrl,

userId,

organizationId,

name: name || null,

protocol,

remotePort: remotePort || null,

lastSeenAt: new Date(),

createdAt: new Date(),

updatedAt: new Date(),

};

await db.insert(tunnels).values(tunnelRecord);

return json({ success: true, tunnelId: tunnelRecord.id });

} catch (error) {

console.error("Tunnel registration error:", error);

return json({ error: "Internal server error" }, { status: 500 });

}

```

  • It checks if the tunnel exists in the database.

```ts

// Check if tunnel already exists in database

const [existingTunnel] = await db

.select()

.from(tunnels)

.where(eq(tunnels.url, tunnelUrl));

const isReconnection = !!existingTunnel;

```

  • Limit is checked here-:

```ts

// Check limits only for NEW tunnels (not reconnections)

if (!isReconnection) {

// Count active tunnels from Redis SET

const activeCount = await redis.scard(setKey);

console.log(

[TUNNEL LIMIT CHECK] Active count in Redis: ${activeCount},

);

```

  • Redis is checked for existing tunnel to check for reconnection.

```ts

// Check limits only for NEW tunnels (not reconnections)

if (!isReconnection) {

// Count active tunnels from Redis SET

const activeCount = await redis.scard(setKey);

console.log(

[TUNNEL LIMIT CHECK] Active count in Redis: ${activeCount},

);

```

  • If the tunnel limit is exceeded, it pops up the tunnel limit error.

```ts

if (activeCount >= tunnelLimit) {

console.log(

[TUNNEL LIMIT CHECK] REJECTED - ${activeCount} >= ${tunnelLimit},

);

return json(

{

error: Tunnel limit reached. The ${currentPlan} plan allows ${tunnelLimit} active tunnel${tunnelLimit > 1 ? "s" : ""}.,

},

{ status: 403 },

);

```

  • If the limit is not exceeded, it triggers a the Insert Statement without locking transactions from other request

```ts

await db.insert(tunnels).values(tunnelRecord);

```

  • If parallel requests are made by the wshandler in /outray/outray-main/apps/tunnel/src/core/WSHandler.ts from the command line app. A request can work on a non updated row because th

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality none, integrity low, availability none.

CVSS metrics in full

The score comes from this 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: 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.
  • Attack requirements: None — no deployment-specific condition has to hold.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Confidentiality impact: None.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2026-22820 is classified as CWE-367: Time-of-check Time-of-use Race Condition. The state checked and the state acted upon can differ, because it may change between the two steps.

Affected software

CVE-2026-22820 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 (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-367: Time-of-check Time-of-use Race Condition) in other software:

Details

Severity LOW
CVSS Score 3.7
CVSS 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
CWE CWE-367
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-22820 carries CVSS 3.7 Low 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-22820 →

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