# nebula-mesh: CA private key not zeroized on web mobile-bundle error paths

Advisory record · `GHSA-2p2f-px33-4vv5`

- **Identifiers:** `GHSA-2p2f-px33-4vv5` · `CVE-2026-53604` · `GO-2026-5984`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-212](https://cwe.mitre.org/data/definitions/212.html) · [CWE-316](https://cwe.mitre.org/data/definitions/316.html)
- **Tags:** [CWE-212](https://agentprime.io/advisories/tag/cwe-212.md) · [CWE-316](https://agentprime.io/advisories/tag/cwe-316.md)
- **Published:** 14 Jul 2026
- **Updated:** 21 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Jul 2026, 20:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/forgekeep/nebula-mesh` (Go): affected `<0.3.8`; fixed in `0.3.8`

## 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

- 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2p2f-px33-4vv5)

## Sources

- [GitHub Advisory Database: GHSA-2p2f-px33-4vv5](https://github.com/advisories/GHSA-2p2f-px33-4vv5)
- [OSV: GHSA-2p2f-px33-4vv5](https://osv.dev/vulnerability/GHSA-2p2f-px33-4vv5)
- <https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-2p2f-px33-4vv5>
- <https://github.com/forgekeep/nebula-mesh/commit/1f1ab9aa8472239763d967e3d50a3cd53a1a79b9>
- <https://github.com/forgekeep/nebula-mesh>
- <https://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.8>

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-2p2f-px33-4vv5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2p2f-px33-4vv5/>. Everything for agents: <https://agentprime.io/llms.txt>.