Cross-site Request Forgery (CSRF) Affecting python311-Authlib package, versions <1.3.1-150600.3.14.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.27% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES157-PYTHON311AUTHLIB-15435304
  • published6 Mar 2026
  • disclosed5 Mar 2026

Introduced: 5 Mar 2026

CVE-2025-68158  (opens in a new tab)
CWE-352  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 python311-Authlib to version 1.3.1-150600.3.14.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python311-Authlib package and not the python311-Authlib package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

Authlib is a Python library which builds OAuth and OpenID Connect servers. In versions 1.0.0 through 1.6.5, cache-backed state/request-token storage is not tied to the initiating user session, so CSRF is possible for any attacker that has a valid state (easily obtainable via an attacker-initiated authentication flow). When a cache is supplied to the OAuth client registry, FrameworkIntegration.set_state_data writes the entire state blob under state{app}_{state}, and get_state_data ignores the caller’s session altogether. This issue has been patched in version 1.6.6.

CVSS Base Scores

version 3.1