CVE-2025-30215
Critical · 9.6CVSS
9.6
EPSS
0.6%
Published
Apr 16, 2025
CISA due date
—
Cloudanix analysis
A messaging server let some users reach in and delete or change data belonging to other users, and the problem is now fixed by installing a newer version.
- Exploitation
- Remote Authenticated
- Attacker needs
- Low Privilege
- Complexity
- Low
- Impact
- Data Tampering
- Component
- Network Service
- Class
- Authorization Bypass
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Missing authorization checks on JetStream management APIs in the $JS. subject namespace allowed any authenticated user with JS permissions in one account to execute administrative actions including data destruction against JetStream assets belonging to any other account.
Why it matters to the business
Attackers can destroy messaging streams and other assets across organizational boundaries, causing data loss, service outages, and potential compliance violations in environments that rely on NATS for multi-tenant messaging.
How an attack unfolds
An attacker obtains JetStream management permissions in a regular account, then issues specially crafted requests to unprotected JS API endpoints; the server fails to enforce account isolation and applies the destructive operation to assets in other accounts.
How to fix it
Upgrade nats-server to version 2.10.27 or 2.11.1 (commit dae965ac1a6e313dc93650f76966ff0776cf85cc). Until the upgrade can be performed, restrict JetStream management permissions to the minimum set of trusted accounts and monitor $JS. API traffic.
How to confirm the fix worked
Confirm the running nats-server binary reports version 2.10.27 or newer; attempt cross-account JS API operations from a test account and verify they are rejected; review server configuration for account isolation settings.
Typical attack path
- Obtain a NATS user with JetStream management permissions in any account
- Identify or guess target stream or consumer names in another account
- Send crafted JS API requests using the $JS. subject namespace
- Trigger data destruction or other administrative actions on foreign assets
How to detect it
Search NATS server logs and JetStream audit records for $JS. API requests originating from accounts that should not have cross-account access; look for unexpected deletion or configuration-change operations on streams and consumers not owned by the requesting account.
What your security team should do
- Immediately schedule upgrade to 2.10.27 or 2.11.1 across all NATS deployments
- Audit and reduce the number of accounts granted JetStream management permissions
- Enable detailed JetStream API logging and retain logs for at least 90 days
- Test disaster-recovery procedures for stream recreation in case of destructive abuse
The record
NATS-Server is a High-Performance server for NATS.io, the cloud and edge native messaging system. In versions starting from 2.2.0 but prior to 2.10.27 and 2.11.1, the management of JetStream assets happens with messages in the $JS. subject namespace in the system account; this is partially exposed into regular accounts to allow account holders to manage their assets. Some of the JS API requests were missing access controls, allowing any user with JS management permissions in any account to perform certain administrative actions on any JS asset in any other account. At least one of the unprotected APIs allows for data destruction. None of the affected APIs allow disclosing stream contents. This vulnerability is fixed in v2.11.1 or v2.10.27.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Go | github.com/nats-io/nats-server/v2 | 2.11.0-RC.1 | 2.11.1 |
| Go | github.com/nats-io/nats-server/v2 | 2.2.0 | 2.10.27 |
| Bitnami | nats | 2.2.0 | 2.11.1 |
| Chainguard | nats-server | 0 | 2.12.1-r1 |
| Chainguard | nats-server-compat | 0 | 2.12.1-r1 |
| Chainguard | nats-server-fips | 0 | 2.12.1-r0 |
| Chainguard | nats-top | 0 | 0.6.3-r3 |
| Chainguard | nats-top-compat | 0 | 0.6.3-r3 |
| Chainguard | nats-top-fips | 0 | 0.6.3-r2 |
| Chainguard | nats-top-fips-compat | 0 | 0.6.3-r2 |
| Chainguard | prometheus-nats-exporter | 0 | 0.17.2-r2 |
| Chainguard | telegraf-1.31 | 0 | 1.31.3-r15 |
| Chainguard | telegraf-1.32 | 0 | 1.32.3-r13 |
| Chainguard | telegraf-1.33 | 0 | 1.33.3-r8 |
| Chainguard | telegraf-1.34 | 0 | 1.34.2-r1 |
| Debian:12 | nats-server | 0 | No fix |
| Debian:13 | nats-server | 0 | 2.10.27-1 |
| Wolfi | nats-server | 0 | 2.12.1-r1 |
| Wolfi | nats-server-compat | 0 | 2.12.1-r1 |
| Wolfi | nats-top | 0 | 0.6.3-r3 |
| Wolfi | nats-top-compat | 0 | 0.6.3-r3 |
| Wolfi | prometheus-nats-exporter | 0 | 0.17.2-r2 |
| Wolfi | telegraf-1.31 | 0 | 1.31.3-r15 |
| Wolfi | telegraf-1.32 | 0 | 1.32.3-r13 |
| Wolfi | telegraf-1.33 | 0 | 1.33.3-r8 |
| Wolfi | telegraf-1.34 | 0 | 1.34.2-r1 |
| go | github.com/nats-io/nats-server/v2 | 2.11.0-RC.1 | 2.11.1 |
| go | github.com/nats-io/nats-server/v2 | 2.2.0 | 2.10.27 |
| openSUSE:Tumbleweed | govulncheck-vulndb | 0 | 0.0.20250422T152923-1.1 |
Related vulnerabilities
- CVE-2026-27571 NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging… Also affects github.com/nats-io/nats-server/v2
- CVE-2022-29946 NATS.io NATS Server before 2.8.2 and Streaming Server before 0.24.6 could allow a remote… Also affects github.com/nats-io/nats-server/v2
- CVE-2023-46129 NATS.io is a high performance open source pub-sub distributed communication technology… Also affects github.com/nats-io/nats-server/v2
- CVE-2022-26652 NATS nats-server before 2.7.4 allows Directory Traversal (with write access) via an… Also affects github.com/nats-io/nats-server/v2
- CVE-2022-24450 NATS nats-server before 2.7.2 has Incorrect Access Control. Also affects github.com/nats-io/nats-server/v2
- CVE-2026-33249 NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging… Also affects nats-top
- CVE-2026-33248 NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging… Also affects nats-top
- CVE-2026-33222 NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging… Also affects nats-top