CVE-2026-41425 | Authlib up to 1.6.10 authlib.integrations.starlette_client.OAuth cross-site request forgery
VulDBArchived Apr 24, 2026✓ Full text saved
A vulnerability described as problematic has been identified in Authlib up to 1.6.10 . Affected by this vulnerability is the function authlib.integrations.starlette_client.OAuth . Such manipulation leads to cross-site request forgery. This vulnerability is documented as CVE-2026-41425 . The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-359547 · CVE-2026-41425 · GCVE-0-2026-41425
AUTHLIB UP TO 1.6.10 AUTHLIB.INTEGRATIONS.STARLETTE_CLIENT.OAUTH CROSS-SITE REQUEST FORGERY
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.7 $0-$5k 0.84+
Summaryinfo
A vulnerability classified as problematic has been found in Authlib up to 1.6.10. Affected by this issue is the function authlib.integrations.starlette_client.OAuth. Performing a manipulation results in cross-site request forgery. This vulnerability is reported as CVE-2026-41425. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Detailsinfo
A vulnerability was found in Authlib up to 1.6.10. It has been classified as problematic. This affects the function authlib.integrations.starlette_client.OAuth. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.6.11, there is no CSRF protection on the cache feature in authlib.integrations.starlette_client.OAuth. This vulnerability is fixed in 1.6.11.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-41425 since 04/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 1.6.11 eliminates this vulnerability.
Productinfo
Name
Authlib
Version
1.6.0
1.6.1
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
1.6.10
Website
Product: https://github.com/authlib/authlib/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Authlib 1.6.11
Timelineinfo
04/20/2026 CVE reserved
04/24/2026 +4 days Advisory disclosed
04/24/2026 +0 days VulDB entry created
04/24/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-41425 (🔒)
GCVE (CVE): GCVE-0-2026-41425
GCVE (VulDB): GCVE-100-359547
Entryinfo
Created: 04/24/2026 21:56
Changes: 04/24/2026 21:56 (63)
Complete: 🔍
Cache ID: 99:662:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸