# NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers

Advisory record · `GHSA-55h8-8g96-x4hj`

- **Identifiers:** `GHSA-55h8-8g96-x4hj` · `BIT-nats-2026-33246` · `CVE-2026-33246` · `GO-2026-4830`
- **State:** Confirmed
- **Severity:** CVSS 6.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-290](https://cwe.mitre.org/data/definitions/290.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 24 Mar 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Mar 2026, 21:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/nats-io/nats-server/v2` (Go): affected `<2.11.15 || >=2.12.0-RC.1, <2.12.6`; fixed in `2.11.15`, `2.12.6`
- `github.com/nats-io/nats-server` (Go): affected `all versions`; no fixed version yet

## Machine-written summary

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

> NATS server versions before 2.11.15 and from 2.12.0-RC.1 before 2.12.6 are affected by a flaw where leafnode connections can spoof the Nats-Request-Info identity header. A leafnode connected to a server is not fully trusted, yet its identity claims were propagated unchecked, so clients relying on that header can be deceived about who sent a message. Upgrade github.com/nats-io/nats-server/v2 to 2.11.15 or 2.12.6. No workaround is listed.

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

- 6.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-55h8-8g96-x4hj)

## Sources

- [GitHub Advisory Database: GHSA-55h8-8g96-x4hj](https://github.com/advisories/GHSA-55h8-8g96-x4hj)
- [OSV: GHSA-55h8-8g96-x4hj](https://osv.dev/vulnerability/GHSA-55h8-8g96-x4hj)
- <https://github.com/nats-io/nats-server/security/advisories/GHSA-55h8-8g96-x4hj>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33246>
- <https://advisories.nats.io/CVE/secnote-2026-08.txt>
- <https://github.com/nats-io/nats-server>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-55h8-8g96-x4hj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-55h8-8g96-x4hj/>. Everything for agents: <https://agentprime.io/llms.txt>.
