Authlib OAuth 2.0 has Open Redirect in Authorization API that allows attacker-controlled redirect_uri through unsupported response_type (CVE-2026-41479)
Authlib OAuth 2.0 authorization endpoint contains an open redirect vulnerability triggered by requests using unsupported response_type values with attacker-controlled redirect_uri parameters. This flaw occurs before client validation and redirect URI checks, allowing unauthenticated attackers to cause the server to issue a 302 redirect to arbitrary URLs. The vulnerability affects Authlib versions prior to 1.6.10 and certain 1.7.0 versions.
AI Analysis
Technical Summary
The vulnerability in Authlib's OAuth 2.0 authorization server arises because the method get_authorization_grant() raises an UnsupportedResponseTypeError containing the raw redirect_uri from the request before any client lookup or redirect URI validation occurs. The OAuth2Error handler then automatically issues a 302 redirect to this attacker-controlled URI. This allows an unauthenticated attacker to exploit the authorization endpoint as an open redirect by sending a request with an unsupported response_type and a malicious redirect_uri. The issue was confirmed in version 1.6.6 and reproduced on the current HEAD at the time of reporting. The vulnerability is reachable through normal OAuth2 authorization flows in Flask and Django integrations using Authlib.
Potential Impact
An attacker can cause the authorization endpoint to redirect users to arbitrary URLs without authentication or client validation. This open redirect can facilitate phishing attacks or redirect users to malicious sites, potentially undermining user trust and security. There is no direct compromise of user credentials or tokens from this vulnerability alone.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, applications should carefully validate and restrict redirect_uri parameters and avoid relying solely on Authlib's default error handling for unsupported response types. Monitoring Authlib's official channels for patches addressing CVE-2026-41479 is recommended.
Authlib OAuth 2.0 has Open Redirect in Authorization API that allows attacker-controlled redirect_uri through unsupported response_type (CVE-2026-41479)
Description
Authlib OAuth 2.0 authorization endpoint contains an open redirect vulnerability triggered by requests using unsupported response_type values with attacker-controlled redirect_uri parameters. This flaw occurs before client validation and redirect URI checks, allowing unauthenticated attackers to cause the server to issue a 302 redirect to arbitrary URLs. The vulnerability affects Authlib versions prior to 1.6.10 and certain 1.7.0 versions.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Authlib's OAuth 2.0 authorization server arises because the method get_authorization_grant() raises an UnsupportedResponseTypeError containing the raw redirect_uri from the request before any client lookup or redirect URI validation occurs. The OAuth2Error handler then automatically issues a 302 redirect to this attacker-controlled URI. This allows an unauthenticated attacker to exploit the authorization endpoint as an open redirect by sending a request with an unsupported response_type and a malicious redirect_uri. The issue was confirmed in version 1.6.6 and reproduced on the current HEAD at the time of reporting. The vulnerability is reachable through normal OAuth2 authorization flows in Flask and Django integrations using Authlib.
Potential Impact
An attacker can cause the authorization endpoint to redirect users to arbitrary URLs without authentication or client validation. This open redirect can facilitate phishing attacks or redirect users to malicious sites, potentially undermining user trust and security. There is no direct compromise of user credentials or tokens from this vulnerability alone.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, applications should carefully validate and restrict redirect_uri parameters and avoid relying solely on Authlib's default error handling for unsupported response types. Monitoring Authlib's official channels for patches addressing CVE-2026-41479 is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w8p2-r796-3vmq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-41479"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a5bd3192a4a8d59892850a2
Added to database: 07/18/2026, 19:25:13 UTC
Last enriched: 07/18/2026, 19:27:35 UTC
Last updated: 07/18/2026, 20:59:30 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.