Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-65599: n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured

27
Routine
MEDIUM 6.5UPGRADE

CVE-2026-65599 is a medium-severity flaw (CVSS 6.5) affecting n8n. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 imperson

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 85%)
CISA exploited listNo
WeaknessCWE-312
Published2026-07-22
Last modified2026-10-24
Publisher (CNA): VulnCheck · Vendor: n8n

Share: LinkedIn · X · Reddit

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

n8n n8n UPGRADE
Affected: < 1.123.64 · >= 2.0.0 and < 2.29.8 · 2.30.0
Fixed in: 1.123.64, 2.29.8
Safe to downgrade to: a release before 2.0.0
1. Check installed version
npm ls n8n
2. UPGRADE to 1.123.64
npm install n8n@">=1.123.64"
3. If no update is available yet, DOWNGRADE to a release before 2.0.0
npm view n8n versions npm install n8n@"<2.0.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-65599?

n8n: upgrade to 1.123.64, 2.29.8. Exact commands for each OS are on this page.

Is CVE-2026-65599 being exploited?

CVE-2026-65599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-65599 affect?

CVE-2026-65599 affects n8n. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2026-65599?

Priority 27/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.