CVE-2026-53604
Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-53604 is a high-severity Improper Removal of Sensitive Information Before Storage or Transfer (CWE-212) vulnerability. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to MP-6 (Media Sanitization) and SI-19 (De-identification) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-71717
Vulnerability Data
nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.8, the web handler renderMobileBundle passes the real *pki.CAResolver directly into mobilebundle.Build. Inside Build, resolver.LoadByID decrypts the CA's ed25519 private key into a *pki.CAManager, but Build…
more
never calls CAManager.Wipe() on any return path. 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 already does this correctly: it loads the CAManager, defer caMgr.Wipe(), and wraps it in caManagerResolver. Only the web path is affected. This issue has been patched in version 0.3.8.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 3 OS baselines
V14.2.8V14.3.3
Mitigating Controls (NIST 800-53 r5) AI
Requires sanitization of media before disposal, release, or reuse, directly stopping sensitive information from remaining in resources made available to unauthorized parties.
Mandates removal of specified PII elements from datasets before further use or sharing, addressing a subset of the improper-removal cases.
Access enforcement limits which subjects can read memory locations holding the cleartext data.
Process isolation confines the cleartext data to its own execution domain, shrinking exposure.
Prevents unintended transfer of the cleartext contents through shared memory resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Directly addresses removal of confidential data from process memory and similar in-use contexts before exposure.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Explicit information-deletion control directly addresses improper removal of sensitive data.
Data-masking techniques can substitute for removal when full deletion is impractical.
Security testing can detect cleartext secrets in memory dumps or debug output.
Test-data protection rules require sanitization of production data used in testing.
Classification identifies sensitive data that must be removed before storage or transfer.
Information-transfer rules can require sanitization of sensitive content before sharing.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-212
- V-248580 OL 8 must prevent kernel profiling by unprivileged users. prevents CWE-212
- V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. prevents CWE-212
Oracle Linux 9 (2 rules)
- V-271730 OL 9 must disable storing core dumps. prevents CWE-316
- V-271745 OL 9 must restrict access to the kernel message buffer. prevents CWE-212
RHEL 8 (1 rule)
- V-230269 RHEL 8 must restrict access to the kernel message buffer. prevents CWE-212