Advisory

GHSA-jj8c-mmj3-mmgv

Also known as: CVE-2026-41425, PYSEC-2026-25

Summary

Authlib: Cross-site request forging when using cache

Details

Summary

There is no CSRF protection on the cache feature on most integrations clients.

Details
In authlib.integrations.starlette_client.OAuth, no CSRF protection is set up when using the cache parameter. When _not_ using the cache parameter, the use of SessionMiddleware ties the client to the auth state, preventing CSRF attacks. With the cache, there is no such mechanism. Other integratons have the same issue, it's not just starlette.

The state parameter is taken from the callback URL and the state is fetched from the cache without checking that it is the same client calling the redirect endpoint as was the one that initiated the auth flow.

This issue is documented in RFC 6749 section 10.12:
https://datatracker.ietf.org/doc/html/rfc6749#section-10.12

PoC

  • Set up a Starlette integration with a cache
  • The attacker starts the auth flow up until before the callback URL is followed.
  • The attacked sends the redirect URL to the victim
  • The victim now completes the authorisation

Impact
This impacts all users that use the cache to store auth state.

All users will be vulnerable to CSRF attacks and may have an attacker's account tied to their own.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-16 22:38 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

authlib

PyPI · All systems

Affected

  • introduced 0, fixed 1.6.11 (ecosystem)

Fixed versions

1.6.11

Fix

  • Fixed version 1.6.11
    pip install --upgrade authlib==1.6.11

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