Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

QTINeon has unauthenticated relay-to-host amplification via unbounded RECONNECT_REQUEST forwarding

CVE-2026-54609GHSA-85rg-p3fr-xc2f

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm qti-neon

    Affected
    >= 1.0.0, <= 1.0.0
    Fixed in
    no fixed version recorded

  • PyPI qti-neon

    Affected
    >= 1.0.0, <= 1.0.0
    Fixed in
    no fixed version recorded

  • Maven com.quietterminal:qti-neon

    Affected
    >= 1.0.0, <= 1.0.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS
  • CVE-2026-54609: 0.46% estimated exploitation activity in the next 30 days; percentile 39.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact The relay's reconnect handler forwards every RECONNECTREQUEST to the host without deduplication or a size cap on the pendingReconnects map, unlike the connect flow which guards against this with maxPendingConnections. An unauthenticated attacker who knows a valid session ID can send RECONNECTREQUEST packets from many spoofed source addresses; each packet that passes the session lookup is forwarded to the host as a new reconnect attempt. Because the per-source rate limiter assigns a fresh token bucket to each spoofed IP, it provides no protection. The host receives one forwarded packet per spoofed source per cleanup cycle, making the relay an amplification vector for denial-of-service against the host. The host's real address is never exposed to clients by design, so this is the primary viable DoS path against it. A secondary issue: once more than maxRateLimiters spoofed IPs are seen, performCleanup calls rateLimiters.clear(), resetting rate limit state for all sources…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-85rg-p3fr-xc2f

  2. Revision 1 · created ·

    Published from osv record GHSA-85rg-p3fr-xc2f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54609

Advisory: QTINeon has unauthenticated relay-to-host amplification via unbounded RECONNECT_REQUEST forwarding
IDs: CVE-2026-54609, GHSA-85rg-p3fr-xc2f
Record: https://patchnext.com/advisories/cve-2026-54609 (revision 2, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm qti-neon: affected >= 1.0.0, <= 1.0.0
- PyPI qti-neon: affected >= 1.0.0, <= 1.0.0
- Maven com.quietterminal:qti-neon: affected >= 1.0.0, <= 1.0.0

## Suggested inspection (read-only)
- `npm ls qti-neon --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `python -m pip show qti-neon`: prints the installed version. Run with the environment that serves production active.
- Maven com.quietterminal:qti-neon: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on qti-neon, com.quietterminal:qti-neon.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-85rg-p3fr-xc2f (OSV record GHSA-85rg-p3fr-xc2f lists affected ranges: Maven com.quietterminal:qti-neon >=1.0.0 =1.0.0 =1.0.0 <=1.0.0)
- Verified: https://github.com/advisories/GHSA-85rg-p3fr-xc2f (GitHub-reviewed advisory GHSA-85rg-p3fr-xc2f lists affected ranges: Maven com.quietterminal:qti-neon >=1.0.0 =1.0.0 =1.0.0 <=1.0.0)

Commands are suggestions: review each one before running it.

Loading voting…