Approved changes feed: RSS · Atom

cpe:2.3:a:@fastify/oauth2:@fastify/oauth2:*:*:*:*:*:*:*:*

part: a version: * update: *

Vendor@Fastify/Oauth2 (7a261bb6-8f24-5a95-806f-26740988c87c)
Product@Fastify/Oauth2 (b2957676-151c-50dc-b6c1-e0f4c681fba1)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-110008 vulnerable 2026-11-03 10:16:01.262507 @fastify/oauth2 vulnerable to Login CSRF via OAuth state cookie not cleared after callback
MEDIUM (4.2)
@fastify/oauth2 is a Fastify wrapper for OAuth2 login flows. In versions 7.2.0 through 8.3.1, the state and code-verifier cookies are set without a Path attribute at a login route with two or more path segments, while the clearing step at the OAuth callback writes them with a root path, so the original cookies survive the callback and the documented single-use guarantee for the state value does not hold. A state value an attacker learns stays valid for the rest of the browser session, letting the attacker drive their own authorization flow in the victim's browser and sign the victim in to the attacker's account (login CSRF). The issue is fixed in @fastify/oauth2 8.3.2, and users should upgrade to 8.3.2 or later. As a workaround, set an explicit cookie path so the set and the clear name the same cookie.
Published: 2026-10-19T13:24:27.988Z
Updated: 2026-10-19T14:26:45.991Z
Reference links
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 JSON directly

Open this panel to browse, search, copy or download the JSON record.