CVE-2026-48025 nebula-mesh: Decrypted CA private key persists in heap after signing

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at...

CVE-2026-48025 nebula-mesh: Decrypted CA private key persists in heap after signing

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at...

CVE-2026-48025 nebula-mesh: Decrypted CA private key persists in heap after signing

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at...

CVE-2026-48025

CVE-2026-48025 (nebula-mesh) describes a memory-safety issue in versions prior to 0.3.7 where decrypted CA private keys (ed25519.PrivateKey) are constructed and stored in memory by the CAManager and not wiped after use. The problem arises when internal/pki/resolver.go constructs CAManager with th...

CVE-2026-48025

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at...

CVE-2024-14041

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM CRYSTALS-Kyber routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec. An...

EUVD-2024-55702

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM CRYSTALS-Kyber routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec. An...

CVE-2024-14041 ML-KEM (Kyber) decapsulation leaks private key information through non-constant-time division in message decoding and ciphertext compression (KyberSlash)

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM CRYSTALS-Kyber routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec. An...

CVE-2024-14041

Bouncy Castle for Java versions 1.73 to before 1.78 is affected by a timing-side-channel in ML-KEM (CRYSTALS-Kyber) decapsulation. Three routines divide secret-derived polynomial coefficients by the modulus q: Poly.toMsg (decoding the decrypted message) and the ciphertext compression routines Pol...

CVE-2024-14041

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM CRYSTALS-Kyber routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec. An...

CVE-2024-14041 ML-KEM (Kyber) decapsulation leaks private key information through non-constant-time division in message decoding and ciphertext compression (KyberSlash)

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM CRYSTALS-Kyber routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec. An...

NPM: n8n: Google Service Account Private Key Exposed in JWT Header

NPM: n8n: Google Service Account Private Key Exposed in JWT Header vulnerability discovered by ? in WordPress Npm n8n versions 1.123.64...

GHSA-9R8P-H6CC-6QHM n8n: Google Service Account Private Key Exposed in JWT Header

Impact When n8n was configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field which should only have held a key identifier. Since JWT headers were Base64-encoded rather than encrypted, the key could be recovered by anything that...

n8n: Google Service Account Private Key Exposed in JWT Header

Impact When n8n was configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field which should only have held a key identifier. Since JWT headers were Base64-encoded rather than encrypted, the key could be recovered by anything that...

Duplicate Advisory: Google Service Account Private Key Exposed in JWT Header

Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-9r8p-h6cc-6qhm. This link is maintained to preserve external references. Original Description n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a...

GHSA-MHVH-GWHR-76PW Duplicate Advisory: Google Service Account Private Key Exposed in JWT Header

Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-9r8p-h6cc-6qhm. This link is maintained to preserve external references. Original Description n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a...

CVE-2026-65599

n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field intended only for a key identifier. Because JWT headers are Base64-encoded...

CVE-2026-65599

n8n is affected by a credential exposure in versions before 1.123.64, 2.29.8, and 2.30.1. When configured with a Google Service Account key, the full PEM private key was incorrectly placed in the JWT header’s kid field (intended as a key identifier). JWT headers are Base64-encoded, not encrypted,...

CVE-2026-65599 n8n before 1.123.64, 2.29.8, and 2.30.1 Credential Exposure via JWT Header

n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field intended only for a key identifier. Because JWT headers are Base64-encoded...

EUVD-2026-47643

n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field intended only for a key identifier. Because JWT headers are Base64-encoded...