CVE-2026-112362

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-110753 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

@fastify/express is a Fastify plugin that runs Express middleware inside Fastify. In versions 4.0.5 through 4.0.8, when Fastify runs with the non-default ignoreDuplicateSlashes option enabled, the plugin matches path-scoped Express middleware against a URL whose duplicate-slash normalization has also collapsed the separator after an absolute-form request target's scheme, so Fastify's router resolves the request to the scoped path and runs the handler while the Express layer no longer sees that path. As a result, a request using an absolute-form target can reach a handler on a scoped route such as an admin path while the middleware for authentication, authorization, or rate limiting is skipped. An unauthenticated attacker needs only the non-default ignoreDuplicateSlashes option to be enabled. The issue is fixed in @fastify/express 4.0.9, and users should upgrade to 4.0.9 or later. As a workaround, enforce authentication in a Fastify hook such as preHandler that runs after the router resolves the request, or leave ignoreDuplicateSlashes at its default.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 27, 2026

Last Modified

November 4, 2026

Advisory Details (2)

Auto-updated Oct 27, 2026
Fix named in the CVE record. Sources: github.
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
GitHub advisoryMentions a patch (unverified)

@fastify/express vulnerable to path-scoped middleware bypass via absolute-form request targets · Advisory · fastify/fastify-express · GitHub

https://github.com/fastify/fastify-express/security/advisories/GHSA-6h42-57hq-9746

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 05:57 UTCEchelonGraph re-scored
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-11-12 04:26 UTCEchelonGraph re-scored
  4. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-11-11 02:51 UTCEchelonGraph re-scored
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-11-10 01:07 UTCEchelonGraph re-scored
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-11-08 23:33 UTCEchelonGraph re-scored
  10. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-11-07 22:01 UTCEchelonGraph re-scored
  12. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-11-06 20:30 UTCEchelonGraph re-scored
  14. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-11-05 23:25 UTCOSV refresh
  16. 2026-11-05 18:58 UTCEchelonGraph re-scored
  17. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-11-04 17:27 UTCEchelonGraph re-scored
  19. 2026-11-04 17:16 UTCEchelonGraph re-scored
  20. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-11-04 01:49 UTCEchelonGraph re-scored
  22. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-11-03 00:18 UTCEchelonGraph re-scored
  24. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-11-01 22:46 UTCEchelonGraph re-scored
Show 13 more
  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-31 21:15 UTCEchelonGraph re-scored
  3. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-30 19:44 UTCEchelonGraph re-scored
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-29 18:13 UTCEchelonGraph re-scored
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-28 16:41 UTCEchelonGraph re-scored
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-27 12:26 UTCEchelonGraph re-scored
  11. 2026-10-27 12:01 UTCENISA EUVD ID recordedEUVD-2026-110753 · Source: ENISA EUVD
  12. 2026-10-27 11:35 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
  13. 2026-10-27 11:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-112362?
CVE-2026-112362 is a critical-severity vulnerability; its CVE record was published on October 27, 2026. @fastify/express is a Fastify plugin that runs Express middleware inside Fastify. In versions 4.0.5 through 4.0.8, when Fastify runs with the non-default ignoreDuplicateSlashes option enabled, the plugin matches path-scoped Express middleware against a URL whose duplicate-slash normalization has…
When was the CVE record for CVE-2026-112362 published?
The CVE record for CVE-2026-112362 was published on October 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 4, 2026; the record at its source may have been updated since.
Is CVE-2026-112362 actively exploited?
CVE-2026-112362 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112362?
CVE-2026-112362 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112362?
The CVE record for CVE-2026-112362 names the fix: "The issue is fixed in @fastify/express 4.0.9, and users should upgrade to 4.0.9 or later."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-112362

Explore →

Is Your Infrastructure Affected by CVE-2026-112362?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs