Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.26% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-86080High confidence
n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open
n8n-io · n8n
Official source article: GitHub GHSA-5M98-CGCR-XX3Q ↗. Check the applicable product and release in the original source.
6.3MediumCVSS 4.0
Scheduled
Mitigation availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs n8n-io n8n and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmn8n | < 1.123.76 | 1.123.76 | GitHub advisory ↗upstream repository advisory · 10 Sep 2026 |
| npmn8n | >= 2.38.0, < 2.38.2 | 2.38.2 | GitHub advisory ↗upstream repository advisory · 10 Sep 2026 |
| npmn8n | >= 2.0.0, < 2.37.7 | 2.37.7 | GitHub advisory ↗upstream repository advisory · 10 Sep 2026 |
| npmn8n | SEMVER: introduced 0; fixed 1.123.76 | 1.123.76 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmn8n | SEMVER: introduced 2.38.0; fixed 2.38.2 | 2.38.2 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmn8n | SEMVER: introduced 2.0.0; fixed 2.37.7 | 2.37.7 | OSV record ↗aggregator derived · 10 Sep 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Mitigation available01
What, why and how
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and X-Hub-Signature-256 verification accepted deliveries without a stored secret. The affected logic includes packages/nodes-base/nodes/Github/GithubTriggerHelpers.ts and the 422 webhook reuse path. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
What
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and X-Hub-Signature-256 verification accepted deliveries without a stored secret. The affected logic includes packages/nodes-base/nodes/Github/GithubTriggerHelpers.ts and the 422 webhook reuse path. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
Why
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and X-Hub-Signature-256 verification accepted deliveries without a stored secret. The affected logic includes packages/nodes-base/nodes/Github/GithubTriggerHelpers.ts and the 422 webhook reuse path. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
Why
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Verification of Cryptographic Signature → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-347 ↗
CWE-347: Improper Verification of Cryptographic Signature. The product does not verify, or incorrectly verifies, the cryptographic signature for data.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VILowVulnerable-system integrity: A successful attack can cause a limited loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Mitigation available
- Action
- Apply the mitigation in the linked authoritative guidance while planning the vendor's permanent fix.
- Workaround
- A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
Official vendor articles4 stored documents
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Release n8n@1.123.76 · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights n8n@1.123.76 Compare Cho
- Release n8n@2.37.7 · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights n8n@2.37.7 Compare Choos
- Release n8n@2.38.2 · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights n8n@2.38.2 Pre-release P
- GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open · Advisory · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights GitHub Trigger 422 Reuse
04
Evidence and provenance
Published 8 Sept 2026 · Last source change 9 Sept 2026, 13:16 UTC · CWE-347 · Improper Verification of Cryptographic Signature
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-09
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-74276
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2026-74276 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-74276"}
- Vendor guidanceAuthoritative vendor guidance changed: added mitigation: github.com/GHSA-5m98-cgcr-xx3q; added remediation: github.com/GHSA-5m98-cgcr-xx3q.security-advisories@github.com ↗
- Before
- no authoritative guidance recorded
- After
- mitigation: github.com/GHSA-5m98-cgcr-xx3q · remediation: github.com/GHSA-5m98-cgcr-xx3q
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- >= 2.38.0, < 2.38.2; >= 2.0.0, < 2.37.7; < 1.123.76 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- n8n: >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7, < 1.123.76 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.security-advisories@github.com ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Mitigation reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.