Advisory record · GHSA-fhg8-qxh5-7q3w

NATS Server may fail to authorize certain Jetstream admin APIs

CVSS 9.6 CriticalCriticalEPSS 0.0061 · 50th percentile

Critical, because:

  • CVSS score 9.6: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 Apr 2025, 21:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nats-io/nats-server/v2Go>=2.11.0-RC.1, <2.11.1 || >=2.2.0, <2.10.272.11.1, 2.10.27
Identifiers
GHSA-fhg8-qxh5-7q3w · BIT-nats-2025-30215 · CVE-2025-30215 · GO-2025-3600
Weakness (CWE)
CWE-285 · CWE-287 · CWE-306
Published
15 Apr 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The nats-server package (Go module github.com/nats-io/nats-server/v2) is affected from v2.2.0 before 2.10.27, and from 2.11.0-RC.1 before 2.11.1. Any user with permission to publish on the JetStream management subjects, including users in regular accounts, can run certain admin JetStream APIs, such as account purge, server removal, and stream moves, against other accounts. An attacker could destroy JetStream data or disrupt clusters, though the source says stream contents cannot be disclosed. Upgrade to 2.10.27 or 2.11.1.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.6 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0061, the 50th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.