SB2026111656 - Multiple vulnerabilities in authlib
Published: November 16, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 2 vulnerabilities.
1) Use of a broken or risky cryptographic algorithm (CVE-ID: N/A)
CWE-ID: CWE-327 - Use of a Broken or Risky Cryptographic Algorithm
CVSSv4: 6 [CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote user to forge messages that other recipients accept as authenticated by the original sender.
The vulnerability exists due to acceptance of non-committing content-encryption algorithms in authlib.jose ECDH-1PU+A*KW decryption when processing JWE messages with draft algorithms registered. A remote user can use a co-recipient's knowledge of an A128CBC-HS256 message's content-encryption key, substitute A256GCM, C20P, or XC20P, and craft additional authenticated data while reusing the original tag and another recipient's wrapped key to impersonate the sender.
2) Improper Verification of Cryptographic Signature (CVE-ID: N/A)
CWE-ID: CWE-347 - Improper Verification of Cryptographic Signature
CVSSv4: 7 [CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to impersonate OAuth clients and read or modify protected resources of users who approve authorization.
The vulnerability exists due to improper cryptographic signature verification in Authlib's OAuth 1.0 provider when accepting request-selected signature methods with empty client secrets, including for RSA-only clients. A remote attacker can use a public client_id with HMAC-SHA1 signatures keyed by "&" or PLAINTEXT signatures of "&", obtain user approval through an attacker-controlled callback, and append issued token secrets to "&" for subsequent requests to access protected resources.
Remediation
Install update from vendor's website.