CVE-2026-65599

n8n before 1.123.64, 2.29.8, and 2.30.1 Credential Exposure via JWT Header

Products / packages n8n-io n8n

Published 22/07/2026, 11:21:46 UTC

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 01:40:32 UTC

VulnCheck · CVSS:4.0 · 5.1

Assessment vector

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

Severity

medium5.1

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

n8n versions before 1.123.64, 2.29.8, and 2.30.1 have a credential exposure vulnerability when using Google Service Account credentials, allowing an attacker to recover the private key from the JWT header and access authorized Google Cloud resources. The private key is mistakenly placed in the JWT header's kid field. Only instances using Google Service Account credentials are affected.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

Excerpt from the original source description below.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

n8n-io · VulnCheck

n8n

2 ranges

VulnCheck version evidence

Package identity

pkg:npm/n8nExplore n8n →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 1.123.64

semver versions

unaffected

1.123.64

semver versions

Other versions: unaffected

n8n-io · VulnCheck

n8n

2 ranges

VulnCheck version evidence

Package identity

pkg:npm/n8nExplore n8n →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

2.30.0 → before 2.30.1

semver versions

unaffected

2.30.1

semver versions

Other versions: unaffected

n8n-io · VulnCheck

n8n

2 ranges

VulnCheck version evidence

Package identity

pkg:npm/n8nExplore n8n →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

2.0.0-rc.0 → before 2.29.8

semver versions

unaffected

2.29.8

semver versions

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

2 sources

n8n-io/n8n · security/advisories/GHSA-9r8p-h6cc-6qhm

Vendor advisoryVulnCheck

www.vulncheck.com/advisories/n8n-before-credential-exposure-via-jwt-header

Security advisoryVulnCheck

Inside the record

Evidence available

Package identity

Version evidence

Remediation guidance · not supplied

Weakness classification

Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-65599

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-312 ↗

Cleartext Storage of Sensitive Information

VulnCheck

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*

From (inclusive):

After:

Through (inclusive):

Before: 1.123.64

Vulnerable product

cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*

From (inclusive): 2.30.0

After:

Through (inclusive):

Before: 2.30.1

Vulnerable product

cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*

From (inclusive): 2.0.0-rc.0

After:

Through (inclusive):

Before: 2.29.8

Applicability preview

[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*",
            "versionEndExcluding": "1.123.64"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*",
            "versionEndExcluding": "2.30.1",
            "versionStartIncluding": "2.30.0"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*",
            "versionEndExcluding": "2.29.8",
            "versionStartIncluding": "2.0.0-rc.0"
          }
        ]
      }
    ]
  }
]

Contributing organizations · 2

VulnCheck

Assigning organization

2026-10-29

CISA-ADP

Additional data publisher

2026-07-22

Timeline

All times UTC

22 Jul 2026, 11:21
Advisory published
Publication date supplied by the source.
29 Oct 2026, 21:16
Source updated
Latest modification date supplied by the source.
29 Oct 2026, 21:58
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

Reading the signals

Severity · CVSS: Technical impact and attack conditions. The headline is the highest imported catalog score; sources may disagree.
Observed exploitation · KEV: An absent or unavailable KEV listing does not establish that exploitation has not occurred.
Predicted exploitation · EPSS: 0.25% estimated probability in the next 30 days. 2026-10-29 · FIRST EPSS.

CISA-ADP · SSVC

CISA Coordinator · 2026-07-22

Exploitation: none
Automatable: no
Technical Impact: partial

SSVC describes the publisher’s decision context. Your organization’s exposure and priorities may differ.

Record identifiers

Aliases: None recorded

Source evidence

Request a correction or dispute

Start with the assigning organization for this record. Include the CVE ID, the disputed information, and supporting evidence. A dispute does not itself reject a record.

Find the responsible CNA →Official dispute and escalation process ↗

CVE CVE-2026-65599