Cyber Resilience

CVE-2025-68158

CSRF in Authlib ≤ 1.6.6

Public PoCCSRF
Published
08 January 2026
Modified
30 March 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0025 16th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-68158 is a medium-severity CSRF (CWE-352) vulnerability in Authlib Authlib. Its CVSS base score is 5.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-68158 affects Authlib, a Python library for building OAuth and OpenID Connect servers, specifically in versions 1.0.0 through 1.6.5. The vulnerability stems from cache-backed state and request-token storage not being tied to the initiating user session. When a cache is supplied to the OAuth client registry, the FrameworkIntegration.set_state_data function writes the entire state blob under a key like _state_{app}_{state}, while get_state_data ignores the caller's session entirely. This flaw, classified as CWE-352 (Cross-Site Request Forgery), carries a CVSS v3.1 base score of 5.7 (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N) and was published on 2026-01-08.

An attacker can exploit this vulnerability by obtaining a valid state value, which is easily acquired through an attacker-initiated authentication flow. With low privileges (PR:L) and requiring user interaction (UI:R), the attacker can perform a CSRF attack over the network (AV:N). Successful exploitation allows high confidentiality impact (C:H), such as unauthorized access to sensitive state data or tokens not bound to the victim's session.

The issue has been addressed in Authlib version 1.6.6. Security advisories and patch commits, including those at GHSA-fg6f-75jq-6523 and specific GitHub changes like 2808378611dd6fb2532b189a9087877d8f0c0489 and 7974f45e4d7492ab5f527577677f2770ce423228, detail the fix to properly associate state storage with user sessions. Practitioners should upgrade to 1.6.6 or later and review cache configurations in OAuth integrations.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

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

CWE(s)
CWE-352

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-8489Shared CWE-352
CVE-2024-51638Shared CWE-352
CVE-2025-23804Shared CWE-352
CVE-2024-36667Shared CWE-352
CVE-2024-26445Shared CWE-352
CVE-2024-22601Shared CWE-352
CVE-2023-50766Shared CWE-352
CVE-2025-9635Shared CWE-352
CVE-2025-30541Shared CWE-352
CVE-2023-27520Shared CWE-352

Affected Assets

authlib
authlib
≤ 1.6.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement partial match

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

SC-23 Session Authenticity partial match

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.23 Web filtering partial match
mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

A.5.7 Threat intelligence none match
none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References