CVE-2026-110024
MEDIUMDescription
@fastify/jwt is a JWT utility plugin for Fastify. In versions prior to 10.2.5, the top-level sign and verify methods replace the globally configured defaults with the per-call options instead of merging them, so passing any per-call option silently drops every global default that the call does not restate, including temporal protections such as token expiration and maximum accepted token age. A token signed this way carries no expiration claim and never expires, and verification stops enforcing a configured maximum age, so stale or never-expiring tokens are accepted. The route-level decorators for signing and verifying already merge options and are not affected. The issue is fixed in @fastify/jwt 10.2.5, and users should upgrade to 10.2.5 or later.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 8% of all known CVEs.
References
Related Vulnerabilities
Other CWE-613 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-2595 | Critical | 9.8 | 17% | - | - |
| CVE-2023-30403 | High | 7.5 | 14% | - | - |
| CVE-2020-27422 | Critical | 9.8 | 7.9% | - | - |
| CVE-2014-3616 | Medium | 4.3 | 5.7% | - | Fix |
| CVE-2021-3144 | Critical | 9.1 | 5.1% | - | Fix |
| CVE-2021-24019 | High | 8.1 | 3.9% | - | Fix |
Common questions
How do I fix CVE-2026-110024?
No published fix for CVE-2026-110024 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-110024 being actively exploited?
Not that we know of. CVE-2026-110024 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.19% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.
How severe is CVE-2026-110024?
CVE-2026-110024 has a CVSS v3 base score of 6.8, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-110024
Markdown
[](https://tridentstack.com/cve/CVE-2026-110024)HTML
<a href="https://tridentstack.com/cve/CVE-2026-110024"><img src="https://tridentstack.com/cve/badge/CVE-2026-110024.svg" alt="CVE-2026-110024"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-20.