Security readout for executives and security teams
Plain-English summary
A specially formatted web request can reach a protected Fastify route without triggering path-specific authentication or authorization middleware. Applications using affected @fastify/middie versions for access control could expose sensitive data or permit unauthorized changes. Availability is not directly affected.
Executive priority
Treat as an urgent patching priority for exposed Fastify services where middie enforces access control. The vulnerability is remotely reachable, requires no credentials or user interaction, and can affect confidentiality and integrity. Accelerate inventory and upgrade verification, while avoiding claims of an active campaign without further evidence.
Technical view
Versions 9.1.0 through 9.3.3 compare path-scoped middleware against the raw request target, while Fastify routes an absolute-form target using its resolved path. This parsing inconsistency can skip middleware yet still dispatch the intended handler. The issue is classified as CWE-436 and scored CVSS 3.1 9.1.
Likely exposure
Exposure requires a Fastify application using @fastify/middie 9.1.0 through 9.3.3 and relying on path-scoped middleware for security controls. Internet-accessible routes protecting sensitive data or state-changing operations carry the greatest business risk. Deployments outside that version range are reported unaffected.
Exploitation context
An unauthenticated network attacker can potentially bypass path-based controls with an absolute-form request target. The source bundle does not report known active exploitation, and the CVE is not listed as KEV. Exploit prevalence and real-world targeting therefore remain unconfirmed.
Researcher notes
The security boundary fails because middleware and router layers interpret the request target differently. Assessment should focus on version confirmation, middleware mounting paths, and whether authorization is independently enforced within handlers. The supplied sources establish impact and the fixed version but provide no evidence of active exploitation.
Mitigation direction
- Upgrade @fastify/middie to version 9.3.4 or later.
- Prioritize applications using path-scoped middleware for authentication or authorization.
- Review vendor guidance for any additional deployment-specific precautions.
- Avoid relying solely on affected path-scoped middleware for sensitive route authorization until upgraded.
Validation and detection
- Inventory deployed and transitive @fastify/middie versions.
- Identify routes whose access controls depend on path-scoped middie middleware.
- Confirm production dependency resolution uses version 9.3.4 or later.
- Run authorized regression tests verifying protected routes reject alternate request-target forms.
- Review relevant access logs for unexpected unauthenticated access to protected routes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-436: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-85184 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2openjsVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fastify/middie/security/advisories/GHSA-hx87-8wv7-pjv8CVE reference, openjs
- https://cna.openjsf.org/security-advisories.htmlCVE reference, openjs
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Interpretation Conflict
Interpretation Conflict represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.