Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1amended

n8n: Google Service Account Private Key Exposed in JWT Header

CVE-2026-65599GHSA-9r8p-h6cc-6qhm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (n8n 2.30.1, 2.29.8, 1.123.64), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm n8n

    Affected
    < 1.123.64>= 2.30.0, < 2.30.1>= 2.0.0-rc.0, < 2.29.8
    Fixed in
    2.29.8, 2.30.1, 1.123.64

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · 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 · score source
EPSS
  • CVE-2026-65599: 0.25% estimated exploitation activity in the next 30 days; percentile 16.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 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. Patches The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Avoid using Google Service Account credentials until the instance is patched. - Rotate any Google Service Account keys that may have been used with an affected n8n…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-9r8p-h6cc-6qhm

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-9r8p-h6cc-6qhm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-65599

Advisory: n8n: Google Service Account Private Key Exposed in JWT Header
IDs: CVE-2026-65599, GHSA-9r8p-h6cc-6qhm
Record: https://patchnext.com/advisories/cve-2026-65599 (revision 3, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: n8n 2.30.1, 2.29.8, 1.123.64. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm n8n: affected < 1.123.64; >= 2.30.0, < 2.30.1; >= 2.0.0-rc.0, < 2.29.8; fixed in 2.29.8, 2.30.1, 1.123.64

## Suggested inspection (read-only)
- `npm ls n8n --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on n8n.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9r8p-h6cc-6qhm (OSV record GHSA-9r8p-h6cc-6qhm lists affected ranges: npm n8n >=0 =2.30.0 =2.0.0-rc.0 <2.29.8 (fixed))
- Verified: https://github.com/advisories/GHSA-9r8p-h6cc-6qhm (GitHub-reviewed advisory GHSA-9r8p-h6cc-6qhm lists affected ranges: npm n8n >=0 =2.30.0 =2.0.0-rc.0 <2.29.8)

Commands are suggestions: review each one before running it.

Loading voting…