@Fastify/Jwt
Approved changes feed: RSS · Atom
cpe:2.3:a:@fastify/jwt:@fastify/jwt:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | @Fastify/Jwt (cf481a99-b2a1-5d83-9a49-9c6e580ed7dc) |
|---|---|
| Product | @Fastify/Jwt (149fcd34-46d1-5631-ae82-464abed19bf1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-110024 |
vulnerable | 2026-11-03 10:16:01.083631 |
@fastify/jwt vulnerable to missing token expiration when per-call options drop global defaults
MEDIUM (6.8)
@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.
Published: 2026-10-18T14:31:38.949Z
Updated: 2026-10-20T18:40:02.655Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.