CVE-2026-84428
Last modified
CVE-2026-84428 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. fastify versions before 5.12.2 implement the case-insensitive nature of HTTP header names by lowercasing names in a route's header schema before compiling it, but the transformation is incomplete: it lowercases the properties keys and the root-level required array, and does not lowercase the trigger and dependent names inside the JSON Schema Draft 7 dependencies keyword. Because Node stores request header names in lowercase, a canonical-case dependency such as requiring an authentication header whenever a privileged-mode header is present never matches, and the presence assertion is silently skipped. EPSS estimates a 0.28% chance of exploitation in the next 30 days.
Description
fastify versions before 5.12.2 implement the case-insensitive nature of HTTP header names by lowercasing names in a route's header schema before compiling it, but the transformation is incomplete: it lowercases the properties keys and the root-level required array, and does not lowercase the trigger and dependent names inside the JSON Schema Draft 7 dependencies keyword. Because Node stores request header names in lowercase, a canonical-case dependency such as requiring an authentication header whenever a privileged-mode header is present never matches, and the presence assertion is silently skipped. An unauthenticated remote client can therefore send the header that activates a privileged branch while omitting the header the dependency was meant to require, bypassing the conditional check. Users should upgrade to fastify 5.12.2 or later.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Fastify | Fastify | < 5.12.2 |
References
- https://cna.openjsf.org/security-advisories.htmlThird Party Advisory
- https://github.com/fastify/fastify/security/advisories/GHSA-9q9j-q6p8-xq58Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-84428?
How severe is CVE-2026-84428?
How do I fix CVE-2026-84428?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-84408QND contains an improper access control vulnerability in a n…8.7
- CVE-2026-8441The WP Review Slider Pro plugin for WordPress is vulnerable …7.5
- CVE-2026-8442The WP Review Slider Pro plugin for WordPress is vulnerable …8.1
- CVE-2026-84423A vulnerability has been found in Casdoor up to 4.0.0. This …7.3
- CVE-2026-84425A vulnerability was found in zhayujie CowAgent up to 2.1.3. …4.3
- CVE-2026-84427A vulnerability was determined in zhayujie CowAgent up to 2.…4.3
- CVE-2026-8443The WP Review Slider Pro plugin for WordPress is vulnerable …8.8
- CVE-2026-84430A security vulnerability has been detected in gouguoa up to …6.3
- CVE-2026-84431A vulnerability was detected in AirAsia MOVE App up to 12.47…4.4
- CVE-2026-84432Concrete CMS 9 through 9.5.2 did not validate an anti-CSRF …5.3
- CVE-2026-84437A vulnerability was found in OpenCart 4.1.0.3/4.1.0.4. The i…3.5
- CVE-2026-84438A vulnerability was determined in OpenCart 4.1.0.3/4.1.0.4. …3.5
Are you affected by CVE-2026-84428?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
