Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-vprv-35vv-q339

HIGH

GHSA-vprv-35vv-q339 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in github.com/nats-io/nats-server/v2. O3 Security confirms whether GHSA-vprv-35vv-q339 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

NATS has pre-auth server panic via leafnode handling

Also known asBIT-nats-2026-33218CVE-2026-33218GO-2026-4837
Published
Mar 24, 2026
Updated
Mar 27, 2026
Affected
3 pkgs
Patched
2 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
🐹github.com/nats-io/nats-server/v2🐹github.com/nats-io/nats-server/v2🐹github.com/nats-io/nats-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Background

NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.

The nats-server allows hub/spoke topologies using "leafnode" connections by other nats-servers.

Problem Description

A client which can connect to the leafnode port can crash the nats-server with a certain malformed message pre-authentication.

Affected Versions

Any version before v2.12.6 or v2.11.15

Workarounds

  1. Disable leafnode support if not needed.
  2. Restrict network connections to your leafnode port, if plausible without compromising the service offered.

References

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/nats-io/nats-server/v2all versions2.11.15
🐹Gogithub.com/nats-io/nats-server/v22.12.0-RC.1&&< 2.12.62.12.6
🐹Gogithub.com/nats-io/nats-serverall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/nats-io/nats-server/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/nats-io/nats-server/v2 to 2.11.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vprv-35vv-q339 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vprv-35vv-q339 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vprv-35vv-q339. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Background NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing. The nats-server allows hub/spoke topologies using "leafnode" connections by other nats-servers. ### Problem Description A client which can connect to the leafnode port can crash the nats-server with a certain malformed message pre-authentication. ### Affected Versions Any version before v2.12.6 or v2.11.15 ### Workarounds 1. Disable leafnode support if not needed. 2. Restrict network connections to your leafnode port, if plausi
O3 Security · Impact-Aware SCA

Is GHSA-vprv-35vv-q339 in your dependencies?

O3 detects GHSA-vprv-35vv-q339 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.