CVE-2026-33216

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, for MQTT deployments using usercodes/passwords: MQTT passwords are incorrectly classified as a non-authenticating identity statement (JWT) and exposed via monitoring endpoints. Versions 2.11.14 and 2.12.6 contain a fix. As a workaround, ensure monitoring end-points are adequately secured. Best practice remains to not expose the monitoring endpoint to the Internet or other untrusted network users.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

March 25, 2026

Last Modified

September 9, 2026

Advisory Details (9)

Auto-updated Jul 3, 2026
Patch available. Sources: github_commit, github, redhat.
redhat

2451448 – (CVE-2026-33216) CVE-2026-33216 nats-server: github.com/nats-io/nats-server: NATS-Server: Information disclosure of MQTT passwords through monitoring endpoints

https://bugzilla.redhat.com/show_bug.cgi?id=2451448
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-33216
github Patch Available

MQTT plaintext password disclosure · Advisory · nats-io/nats-server · GitHub

https://github.com/nats-io/nats-server/security/advisories/GHSA-v722-jcv5-w7mc
github_commit

commit b5b63cfc35a5 (nats-io/nats-server)

Fix landed in nats-io/nats-server commit b5b63cfc35a5 — awaiting tagged release

https://github.com/nats-io/nats-server/commit/b5b63cfc35a57075e09c1f57503d31721bed8099

Patch Availability(3)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/nats-io/nats-server
github.com/nats-io/nats-server/v22.12.6
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.1-1 ... 2.9.19-1 (14 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.27-1, 2.12.4-1, 2.12.6-1, 2.14.1-1, 2.14.3-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nats-server2.10.27-1, 2.12.4-12.12.6-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-09 13:42 UTCVendor advisory
  12. 2026-09-09 12:41 UTCEG score recompute
  13. 2026-09-09 12:41 UTCVendor advisory
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-07 13:24 UTCEG score recompute
  17. 2026-09-07 13:24 UTCVendor advisory
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 14:11 UTCEPSS rescore
  22. 2026-09-01 13:53 UTCEPSS rescore
  23. 2026-09-01 04:39 UTCEPSS rescore
  24. 2026-09-01 04:39 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-24 14:17 UTCEPSS rescore
  7. 2026-08-24 13:31 UTCVendor advisory
  8. 2026-08-24 12:27 UTCEG score recompute
  9. 2026-08-24 12:27 UTCVendor advisory
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 12:21 UTCVendor advisory
  18. 2026-08-17 12:13 UTCEG score recompute
  19. 2026-08-17 12:13 UTCVendor advisory
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 10:13 UTCEG score recompute
  22. 2026-08-16 10:13 UTCVendor advisory
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 13:28 UTCVendor advisory
  26. 2026-08-14 12:30 UTCVendor advisory
  27. 2026-08-14 06:31 UTCEG score recompute
  28. 2026-08-14 06:31 UTCVendor advisory
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-12 20:48 UTCEG score recompute
  31. 2026-08-12 20:48 UTCVendor advisory
  32. 2026-08-12 13:50 UTCEPSS rescore
  33. 2026-08-11 20:52 UTCEG score recompute
  34. 2026-08-11 20:52 UTCVendor advisory
  35. 2026-08-11 03:55 UTCEG score recompute
  36. 2026-08-11 03:55 UTCVendor advisory
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 13:22 UTCVendor advisory
  39. 2026-08-10 12:27 UTCVendor advisory
  40. 2026-08-10 07:54 UTCVendor advisory
  41. 2026-08-09 19:00 UTCEG score recompute
  42. 2026-08-09 19:00 UTCVendor advisory
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-09 06:07 UTCEG score recompute
  45. 2026-08-09 06:07 UTCVendor advisory
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 05:20 UTCEG score recompute
  48. 2026-08-08 05:20 UTCVendor advisory
  49. 2026-08-07 16:27 UTCVendor advisory
  50. 2026-08-06 18:50 UTCEG score recompute
  51. 2026-08-06 18:50 UTCVendor advisory
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 00:57 UTCEG score recompute
  54. 2026-08-06 00:57 UTCVendor advisory
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-04 15:10 UTCEPSS rescore
  57. 2026-08-04 10:38 UTCEPSS rescore
  58. 2026-08-04 02:39 UTCVendor advisory
  59. 2026-08-03 13:44 UTCVendor advisory
  60. 2026-08-03 12:49 UTCEG score recompute
  61. 2026-08-03 12:49 UTCVendor advisory
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-02 15:27 UTCEG score recompute
  64. 2026-08-02 15:27 UTCVendor advisory
  65. 2026-08-02 02:27 UTCEPSS rescore
  66. 2026-08-01 04:16 UTCEPSS rescore
  67. 2026-07-30 16:28 UTCEPSS rescore
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-27 14:13 UTCEPSS rescore
  70. 2026-07-27 13:31 UTCVendor advisory
  71. 2026-07-27 12:41 UTCEG score recompute
  72. 2026-07-27 12:41 UTCVendor advisory
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-25 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-33216?
CVE-2026-33216 is a high vulnerability published on March 25, 2026. NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, for MQTT deployments using usercodes/passwords: MQTT passwords are incorrectly classified as a non-authenticating identity statement (JWT) and exposed via monitoring…
When was CVE-2026-33216 disclosed?
CVE-2026-33216 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33216 actively exploited?
CVE-2026-33216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.6% of all scored CVEs.
What is the CVSS score of CVE-2026-33216?
CVE-2026-33216 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33216, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33216

Explore →

Is Your Infrastructure Affected by CVE-2026-33216?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.