Overview
CVE-2025-30215 is a significant vulnerability affecting NATS-Server, a high-performance server for NATS.io, known for being a cloud and edge native messaging system. This vulnerability was discovered in versions starting from 2.2.0 but prior to 2.10.27 and 2.11.1. It exposes a weakness in the management of JetStream assets, allowing unauthorized access to administrative actions on any JS asset in any other account. This issue affects a wide range of users and organizations that employ NATS-Server within their infrastructure, posing serious risks of system compromise or data destruction.
Vulnerability Summary
CVE ID: CVE-2025-30215
Severity: Critical (9.6)
Attack Vector: Network
Privileges Required: Low
User Interaction: None
Impact: System compromise, potential data leakage, and data destruction
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
NATS-Server | 2.2.0 to 2.10.26
NATS-Server | 2.2.0 to 2.11.0
How the Exploit Works
The vulnerability lies in the management of JetStream assets due to missing access controls. For the affected NATS-Server versions, JetStream assets are managed with messages in the $JS. subject namespace in the system account. Parts of this system are exposed into regular accounts to allow account holders to manage their assets.
However, some of the JS API requests lack appropriate access controls, allowing any user with JS management permissions in any account to perform administrative actions on any JS asset in any other account. While none of the affected APIs allow disclosing stream contents, at least one unprotected API can lead to significant data destruction.
Conceptual Example Code
This is a conceptual example of how the vulnerability might be exploited. This command could theoretically be run by any user with JS management permissions to delete data in another account:
nats request '$JS.api.consumer.delete' '{"stream_name":"TARGET_STREAM","name":"TARGET_CONSUMER"}'
Note that this is a conceptual example and not a literal command. Actual exploitation would likely involve more specific and complex actions.
