GHSA-mhvh-gwhr-76pw
Suggest an improvement- Source
- https://github.com/advisories/GHSA-mhvh-gwhr-76pw
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/07/GHSA-mhvh-gwhr-76pw/GHSA-mhvh-gwhr-76pw.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-mhvh-gwhr-76pw
- Withdrawn
- 2026-07-22T17:59:48Z
- Published
- 2026-07-22T12:32:18Z
- Modified
- 2026-07-22T18:16:06Z
- Severity
-
- 5.1 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L/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:X CVSS Calculator
- Summary
- Duplicate Advisory: Google Service Account Private Key Exposed in JWT Header
- Details
-
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 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 rather than encrypted, the private key could be recovered by anything that logged or inspected the JWT. An attacker who obtained the key could impersonate the service account and access or modify any Google Cloud resource it was authorized to use. Only instances using Google Service Account credentials are affected.
- Database specific
{ "cwe_ids": [ "CWE-312" ], "github_reviewed": true, "github_reviewed_at": "2026-07-22T17:59:48Z", "nvd_published_at": "2026-07-22T12:18:20Z", "severity": "MODERATE" }- References
Affected packages
npm / n8n
Package
- Name
- n8n
- View open source insights on deps.dev
- Purl
- pkg:npm/n8n