CVE-2026-18500 is an authentication and authorization flaw in the @fastify/jwt JSON Web Token plugin for Fastify affecting versions prior to 10.2.2. When an application calls request.jwtVerify({ key }) to enforce verification with a route-specific or domain-specific key, the explicitly supplied per-request verification key can be silently overridden by the plugin’s globally configured secret because the option-merging logic applies the global key last. As a result, routes intended to validate tokens against a distinct verification key may instead accept tokens signed with the global secret. This breaks key separation between authorization domains, such as user and admin token realms, and can allow a token valid for one trust domain to be accepted in another.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.