GHSA-2p2f-px33-4vv5

Suggest an improvement
Source
https://github.com/advisories/GHSA-2p2f-px33-4vv5
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/07/GHSA-2p2f-px33-4vv5/GHSA-2p2f-px33-4vv5.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-2p2f-px33-4vv5
Aliases
  • CVE-2026-53604
Published
2026-07-14T20:05:38Z
Modified
2026-07-14T20:15:13.404622382Z
Severity
  • 8.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
nebula-mesh: CA private key not zeroized on web mobile-bundle error paths
Details

Impact

The web handler renderMobileBundle (internal/web/handlers.go:1325) passes the real *pki.CAResolver directly into mobilebundle.Build. Inside Build (internal/mobilebundle/builder.go:54), resolver.LoadByID decrypts the CA's ed25519 private key into a *pki.CAManager, but Build never calls CAManager.Wipe() on any return path (success or any of the error paths at lines 56, 62, 68, 80, 86, 92, 98, 102, 109, 118, 150).

As a result, when a mobile-bundle request goes through the web UI and Build returns — especially on error (missing network, invalid prefix, DB error, signing failure) — the plaintext CA private key remains on the Go heap, unwiped, until garbage collection. An attacker able to read process memory (core dump, swap, memory-scraping) can recover the CA signing key, which would allow minting arbitrary host certificates for the mesh.

The API handler (internal/api/mobile_bundle.go:74) already does this correctly: it loads the CAManager, defer caMgr.Wipe(), and wraps it in caManagerResolver. Only the web path is affected.

This is the same key-zeroization class previously addressed in GHSA-8h84-fhqq-q58v.

Patches

Add defer caMgr.Wipe() inside mobilebundle.Build immediately after the LoadByID call so every caller (web and API) is protected on all return paths. Ensure CAManager.Wipe() is idempotent, since the API handler also wipes the same manager.

Workarounds

None at the configuration level; requires a code fix.

Resources

  • internal/web/handlers.go:1325
  • internal/mobilebundle/builder.go:54
  • internal/api/mobile_bundle.go:74 (correct reference implementation)
  • Prior related advisory: GHSA-8h84-fhqq-q58v
Database specific
{
    "severity": "HIGH",
    "github_reviewed": true,
    "nvd_published_at": null,
    "github_reviewed_at": "2026-07-14T20:05:38Z",
    "cwe_ids": [
        "CWE-212",
        "CWE-316"
    ]
}
References

Affected packages

Go / github.com/forgekeep/nebula-mesh

Package

Name
github.com/forgekeep/nebula-mesh
View open source insights on deps.dev
Purl
pkg:golang/github.com/forgekeep/nebula-mesh

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.3.8

Database specific

last_known_affected_version_range
"<= 0.3.7"
source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/07/GHSA-2p2f-px33-4vv5/GHSA-2p2f-px33-4vv5.json"