⚠ Withdrawn by GitHub Security Advisories

Withdrawn: July 22, 2026

GHSA-mhvh-gwhr-76pwMediumDisclosed before NVD

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

Published
July 22, 2026
Last Modified
July 22, 2026

📋 Description

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.

🎯 Affected products1

  • npm/n8n:< 1.123.64

🔗 References (4)