CVE-2026-110008

LOWCVSS 4.2 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

@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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-352CWE-459CWE-613

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-19: 110-19
Referenced assets1 URL
Full discourse1 post
  • Ulises Gascón@kom_256

    🚨 Medium-severity security fix in @fastify/oauth2@8.3.2 just released! Patches CVE-2026-110008: @fastify/oauth2 vulnerable to Login CSRF via OAuth state cookie not cleared after callback https://github.com/fastify/fastify-oauth2/security/advisories/GHSA-7fcr-mwg4-pw9q

    00060339
    5.5K followersView on X

Explore more