← Back
CVE-2025-30215
Vulnerability in github.com/nats-io/nats-server/v2 (CVE-2025-30215)
Summary
vulnerability in github.com/nats-io/nats-server/v2 (CVE-2025-30215). Data can be tampered with by attackers. Exploitable via ``ACCOUNT.PURGE``. Mitigation: upgrade to `2.10.27` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-30215** has been found in github.com/nats-io/nats-server/v2.
Attackers can target a specific entry point like ``ACCOUNT.PURGE`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade github.com/nats-io/nats-server/v2 to **2.10.27** or later.
If unsure, ask your IT team or search "github.com/nats-io/nats-server/v2 CVE-2025-30215" on the vendor's site.
CVE-2025-30215 (github.com/nats-io/nats-server/v2) — CWE-285 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `ACCOUNT.PURGE` / `CANCEL_MOVE`
Patched: `2.10.27` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-285) exists in github.com/nats-io/nats-server/v2. Attackers reach the vulnerable code path via ``ACCOUNT.PURGE`` without authentication.
📍 Affected scope
github.com/nats-io/nats-server/v2 — . Attack surface: `ACCOUNT.PURGE` / `CANCEL_MOVE`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **2.10.27**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/nats-io/nats-server/v2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/nats-io/nats-server/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/nats-io/nats-server/v2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/nats-io/nats-server/v2 to 2.10.27ステージング環境で 2.10.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/nats-io/nats-server/v2
[{"type":"SEMVER","events":[{"introduced":"2.2.0"},{"fixed":"2.10.27"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-30215
- package https://github.com/nats-io/nats-server
- web https://github.com/nats-io/nats-server/security/advisories/GHSA-fhg8-qxh5-7q3w
- web https://advisories.nats.io/CVE/secnote-2025-01.txt
- web http://www.openwall.com/lists/oss-security/2025/04/08/5
- web https://osv.dev/vulnerability/GO-2025-3600
- web https://github.com/nats-io/nats-server/commit/3e7e4645a24e829a36b4210f2d7c34dea7f7a424
- web https://github.com/advisories/GHSA-fhg8-qxh5-7q3w