Skip to main content
VulnerabilityPublished

CVE-2026-58211: nats-server · Incorrect Authorization

Affects nats-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.14.3 or 2.12.12 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.3, 2.12.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Upgrade nats-server and nats-io/nats-server to 2.14.3 or 2.12.12.

Affected software

ProductAffectedFixed in
nats-ionats-serverAffected
  • >=2.14.0-RC.1 <2.14.3
Fixed in
  • 2.14.3
nats-ionats-serverAffected
  • <2.12.12
Fixed in
  • 2.12.12
GitHubnats-io/nats-serverpkg:github/nats-io/nats-serverOther threatsAffected
  • <2.12.12
  • >=2.12.0 <2.12.12
  • <2.14.3
  • >=2.12.0 <2.14.3
Fixed in
  • 2.12.12
  • 2.14.3

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.3 or 2.12.12 or later, where this authorization bypass vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.3 and 2.12.12, a client could be registered as the configured no_auth_user through a parser path used when the first client operation was not CONNECT, bypassing user-level connection restrictions such as allowed_connection_types or proxy_required that normal authentication would apply. This issue is fixed in versions 2.14.3 and 2.12.12.

References

Community reviews

Loading reviews…