Advisory

GHSA-fm3f-ch8h-qw8q

Also known as: CVE-2026-81888

Summary

@hono/oauth-providers: OAuth state check fails open on omitted state, enabling login CSRF and forced account linking

Details

Summary

The built-in social login providers accept an OAuth callback even when the state value is absent on both sides, so the anti-CSRF check passes for a callback that never came from a genuine login attempt. This defeats the state-based CSRF protection under default usage.

Details

The state check treated two absent values as a match, so a callback that omits state — and for which no state was ever stored — was allowed to redeem the authorization code. Hono's csrf() middleware does not help: it only inspects form-style requests, while the OAuth callback is a top-level GET navigation it treats as safe.

This affects the google, github, facebook, discord, twitch, linkedin, and msentra providers. The x (Twitter) provider is not exploitable due to its PKCE binding.

Impact

An attacker can make a victim's browser complete an OAuth callback that binds the attacker's identity instead of the victim's, leading to login CSRF (the victim silently acts inside the attacker's account) or forced account linking (the attacker's identity is linked to the victim's account, enabling later sign-in as the victim). Affects applications using an affected provider on @hono/oauth-providers 0.8.5 or earlier.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-08-31 20:30 UTC
Modified
2026-09-15 05:30 UTC

Affected packages and fixes

@hono/oauth-providers

npm · All systems

Affected

  • introduced 0, fixed 0.8.6 (semver)

Fixed versions

0.8.6

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences