CVEPublished 2026-07-22Modified 2026-07-270 articles on news4 live referencesNVD data

CVE-2026-65599N8n · N8n

Vulnerability data via NVD (ingested)

CVSS v3.1
6.5
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS percentile
6
Exploit Prediction Scoring System · top 94% of all CVEs
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.

Timeline
Published 2026-07-22
Modified 2026-07-27

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common). Live host counts are a Premium feature.

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2026-65599 on GitHub.
We haven't classified any articles referencing CVE-2026-65599 yet. The external references above still apply.