← Back
CVE-2026-29785
high
CVSS 7.5
Vulnerability in nats (CVE-2026-29785)
Summary
vulnerability in nats (CVE-2026-29785). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.11.14, 2.12.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-29785** has been found in nats.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade nats to **2.11.14, 2.12.5** or later.
If unsure, ask your IT team or search "nats CVE-2026-29785" on the vendor's site.
CVE-2026-29785 (nats) — CWE-476 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.11.14, 2.12.5` — 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-476) exists in nats.
📍 Affected scope
nats — .
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.11.14, 2.12.5**.
🛡️ 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 'nats' .` 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 'nats' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nats` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade nats to 2.11.14, 2.12.5ステージング環境で 2.11.14, 2.12.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
nats
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.11.14"},{"introduced":"2.12.0"},{"fixed":"2.12.5"}]}]
References
- web https://advisories.nats.io/CVE/secnote-2026-04.txt
- web https://github.com/nats-io/nats-server/commit/a1488de6f2ba6e666aef0f9cce0016f7f167d6a8
- web https://github.com/nats-io/nats-server/security/advisories/GHSA-52jh-2xxh-pwh6
- web https://access.redhat.com/errata/RHSA-2026:21769
- web https://access.redhat.com/errata/RHSA-2026:22347
- web https://access.redhat.com/errata/RHSA-2026:23345
- web https://access.redhat.com/security/cve/CVE-2026-29785
- web https://bugzilla.redhat.com/show_bug.cgi?id=2451444
- web https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29785.json
- web https://nvd.nist.gov/vuln/detail/CVE-2026-29785