CVE-2026-58253: nats-server · Improper Authentication
Affects nats-serverSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 2.12.6 or 2.11.16 soon.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.12.6, 2.11.16, 2.14.0 +1
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
Upgrade nats-server to 2.12.6 or 2.11.16; nats-io/nats-server to 2.14.0, 2.12.7 or 2.11.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nats-ionats-server | Affected
| Fixed in
|
| nats-ionats-server | Affected
| Fixed in
|
GitHubnats-io/nats-serverpkg:github/nats-io/nats-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade nats-server to version 2.14.0, 2.12.7, or 2.11.16 or later to remediate this vulnerability. These versions contain the official fix that prevents authentication bypass when no_auth_user is configured. No other mitigations are indicated by the vendor advisory.
Description
NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.0, 2.12.7, and 2.11.16, when no_auth_user was configured, a parser fast path intended for ordinary client connections could also apply to route or leafnode listeners, allowing an unauthenticated peer to bypass inter-server CONNECT authentication and operate with the privileges associated with that connection type. This issue is fixed in versions 2.14.0, 2.12.7, and 2.11.16.
References
- github.com/nats-io/nats-server/security/advisories/GHSA-38x3-76xf-cq45 (opens in a new tab)
- github.com/nats-io/nats-server/commit/7b81dd455ea95960090a84858c7662827948d1b6 (opens in a new tab)
- github.com/nats-io/nats-server/commit/8b8e1ad4ceed32321e00d4fc6e76be05bc13bca6 (opens in a new tab)
- github.com/nats-io/nats-server/commit/b86147e81710a52b72a7f7275f91d69f723f5cb3 (opens in a new tab)
- github.com/nats-io/nats-server/releases/tag/v2.11.16 (opens in a new tab)
- github.com/nats-io/nats-server/releases/tag/v2.12.7 (opens in a new tab)
- github.com/nats-io/nats-server/releases/tag/v2.14.0 (opens in a new tab)