Your message dated Wed, 28 Oct 2026 09:10:25 +0000
with message-id <[email protected]>
and subject line Bug#1151845: fixed in python-authlib 1.9.1-1
has caused the Debian Bug report #1151845,
regarding python-authlib: CVE-2026-114614 CVE-2026-114615 CVE-2026-114616
CVE-2026-114617 CVE-2026-114618 CVE-2026-114619 CVE-2026-114620
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1151845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151845
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-authlib
Version: 1.7.2-2
X-Debbugs-CC: [email protected]
Severity: important
Tags: security upstream
Hi,
The following vulnerabilities were published for python-authlib.
CVE-2026-104056[0]:
| Authlib version 1.7.2 and below contains a vulnerability where
| discovery JSON metadata is cached without validation or issuer-
| origin binding. This allows a poisoned discovery response to replace
| all endpoint values with attacker-controlled values rather than
| endpoint URLs that share the origin of the configured server
| metadata URL.
CVE-2026-114614[1]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. From 0.13 until 1.8.0,
| authlib.common.security.is_secure_transport() uses a textual prefix
| comparison for loopback HTTP exemptions, so a URL whose userinfo
| begins with a loopback host can be accepted even when its parsed
| host is an external non-loopback system. An external party able to
| supply a URL to OIDC RP-Initiated Logout registration,
| authorization-server metadata validation, or another call site can
| bypass the TLS-required guard and cause cleartext redirection or
| acceptance of cleartext endpoints. The issue does not bypass
| redirect URI exact matching and does not by itself forge tokens or
| authenticate users. The vulnerable
| authlib.common.security.is_secure_transport() implementation in
| authlib/common/security.py misinterprets the userinfo component
| before OIDC RP-Initiated Logout dynamic client registration and
| other consumers enforce transport security. This issue is fixed in
| version 1.8.0.
CVE-2026-114615[2]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. From 1.3.1 until 1.9.0, OctKey.import_key() checks
| asymmetric-key markers only at byte zero while Authlib's PEM loaders
| accept leading whitespace, comments, or a byte-order mark. In
| deployments that use the documented mixed algorithm registry and
| already configure verification with PEM or certificate bytes
| containing such a prefix, an unauthenticated attacker who knows
| those same public-key bytes can use them as an HMAC secret and forge
| HS256 tokens with arbitrary identity or authorization claims. This
| is a bypass of the remediation for CVE-2024-37568. The module-level
| jwt object reaches OctKey.import_key() in
| authlib/jose/rfc7518/oct_key.py, where POSSIBLE_UNSAFE_KEYS fails to
| identify prefixed asymmetric key material. This issue is fixed in
| version 1.9.0.
CVE-2026-114616[3]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. Prior to 1.9.1, Authlib's OctKey.import_key() and HMAC
| signing and verification path accept zero-length key material. If an
| application's secret lookup can return an empty string or empty
| bytes, a remote attacker can compute the deterministic HS256, HS384,
| or HS512 signature for arbitrary token claims and have Authlib treat
| the token as authentic. This issue is fixed in version 1.9.1.
CVE-2026-114617[4]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. Prior to 1.9.0, OpenIDMixin.parse_id_token() reads the
| nonce_supported decision from the untrusted ID token being validated
| and sets the expected nonce to null when that claim is the JSON
| boolean false. In implicit and hybrid relying parties, or
| applications that directly accept externally supplied ID tokens, an
| attacker with a captured validly signed token can bypass the nonce-
| to-session binding and replay the victim's token into an attacker-
| controlled session. Plain authorization code flow is not affected,
| and the token must still pass signature, issuer, and audience
| validation. OpenIDMixin.parse_id_token() trusts nonce_supported in
| both authlib/integrations/base_client/sync_openid.py and
| authlib/integrations/base_client/async_openid.py to disable the
| expected nonce. This issue is fixed in version 1.9.0.
CVE-2026-114618[5]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. Prior to 1.9.0, the default RFC 7523
| JWTBearerGrant.get_audiences() returns an empty list, causing
| JWTBearerGrant.verify_claims() to require only that an aud claim
| exists without matching the current authorization server. An
| attacker holding a legitimate assertion for another service can
| present it to a server that shares the signing key and uses the
| default grant, obtaining an access token across a trust boundary.
| Implementations that override get_audiences() with the server's
| valid audience identifiers are not affected. This issue is fixed in
| version 1.9.0.
CVE-2026-114619[6]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. Prior to 1.9.0,
| OpenIDImplicitGrant.validate_authorization_request() checks the
| client-controlled raw request.payload.scope for openid after the
| parent grant has filtered allowed scopes into request.scope. A
| registered client permitted an ID token response type but not the
| openid scope can add openid to the request, obtain user consent, and
| receive a signed ID token containing the user's subject and allowed
| profile claims. Authorization code flow and deployments that allow
| openid for every client permitted an ID token response are not
| affected. In authlib/oidc/core/grants/implicit.py,
| OpenIDImplicitGrant.validate_authorization_request() checks
| request.payload.scope instead of the filtered request.scope. This
| issue is fixed in version 1.9.0.
CVE-2026-114620[7]:
| Authlib is a Python library which builds OAuth and OpenID Connect
| servers. Prior to 1.9.0, Authlib's RFC 9101 JWTAuthenticationRequest
| passes the unauthenticated, client-controlled request_uri parameter
| to the abstract get_request_object() hook before applying a
| destination or registration policy; the hook itself performs no
| network request, while the documentation demonstrates an
| unrestricted HTTP fetch. In deployments whose integrator implements
| that hook as an unrestricted outbound fetch, a remote attacker who
| knows a valid public client identifier can make the authorization
| server request internal, link-local, or otherwise unintended URLs
| and can distinguish fetch outcomes through different error responses
| and timing. Deployments whose custom hook already applies a secure
| allowlist, destination controls, and retrieval limits are not
| affected. The JWTAuthenticationRequest implementation in
| authlib/oauth2/rfc9101/authorization_server.py forwards request_uri
| to get_request_object() before an application-approved retrieval
| policy accepts the destination. This issue is fixed in version
| 1.9.0.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2026-104056
https://www.cve.org/CVERecord?id=CVE-2026-104056
[1] https://security-tracker.debian.org/tracker/CVE-2026-114614
https://www.cve.org/CVERecord?id=CVE-2026-114614
[2] https://security-tracker.debian.org/tracker/CVE-2026-114615
https://www.cve.org/CVERecord?id=CVE-2026-114615
[3] https://security-tracker.debian.org/tracker/CVE-2026-114616
https://www.cve.org/CVERecord?id=CVE-2026-114616
[4] https://security-tracker.debian.org/tracker/CVE-2026-114617
https://www.cve.org/CVERecord?id=CVE-2026-114617
[5] https://security-tracker.debian.org/tracker/CVE-2026-114618
https://www.cve.org/CVERecord?id=CVE-2026-114618
[6] https://security-tracker.debian.org/tracker/CVE-2026-114619
https://www.cve.org/CVERecord?id=CVE-2026-114619
[7] https://security-tracker.debian.org/tracker/CVE-2026-114620
https://www.cve.org/CVERecord?id=CVE-2026-114620
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-authlib
Source-Version: 1.9.1-1
Done: Stefano Rivera <[email protected]>
We believe that the bug you reported is fixed in the latest version of
python-authlib, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera <[email protected]> (supplier of updated python-authlib
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 28 Oct 2026 10:37:22 +0200
Source: python-authlib
Architecture: source
Version: 1.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Stefano Rivera <[email protected]>
Closes: 1150509 1151845
Changes:
python-authlib (1.9.1-1) unstable; urgency=medium
.
* New upstream release.
- Avoid JWS signature bypass in JsonWebSignature.deserialize_json()
(CVE-2026-96760, Closes: #1150509)
- Avoid bypass in is_secure_transport() (CVE-2026-114614)
- Enforce JOSE key, scope, and audience validation
(CVE-2026-114615, CVE-2026-114618, CVE-2026-114619)
- Avoid jose signature bypass with empty HMAC (CVE-2026-114616)
- Enforce oauth nonce and JAR request validation
(CVE-2026-114617, CVE-2026-114620)
(Closes: #1151845)
- Reject registration access token issued to another client
(CVE-2026-116672)
* Refresh patches.
* Drop patch joserfc-1.7.3.patch, superseded upstream.
* Build-Depend on python3-sphinxcontrib-mermaid.
* Migrate from python3-httpx to python3-httpx2.
- Skip test_falls_back_to_httpx_with_deprecation_warning.
Checksums-Sha1:
913e3eec5683a022b50623b192a229f0375efe0f 2627 python-authlib_1.9.1-1.dsc
e3430c65fad1744d4a7fd8b93c336633a5de9eee 388395
python-authlib_1.9.1.orig.tar.gz
dd865dadd3200f914b4ac7bfaaaa0013f74daa7d 6164
python-authlib_1.9.1-1.debian.tar.xz
3480289d249688ed91919ab6544b253b7850c8cf 7342
python-authlib_1.9.1-1_source.buildinfo
Checksums-Sha256:
1e8daae7a5d318fb1a0d782d3c8a47d151ea03b2b51b65793ab79f6ac3e65ae6 2627
python-authlib_1.9.1-1.dsc
9868306525d9907a3eaf97ff8f5dd754c3cb768e41823dc7f5565abfe3e169fb 388395
python-authlib_1.9.1.orig.tar.gz
3e13019073c4ae715d83fe88a15f0a86e0d588adf9316ecd21a0b1beb8767d31 6164
python-authlib_1.9.1-1.debian.tar.xz
ebc7a140832da2597beccd98e2647596682f46b4d9a3434ce46328d8381b77c7 7342
python-authlib_1.9.1-1_source.buildinfo
Files:
921c6a9d7c7f09674d49e9ddb33ae34a 2627 python optional
python-authlib_1.9.1-1.dsc
b98aa50b344bbc5930540c2017b80e52 388395 python optional
python-authlib_1.9.1.orig.tar.gz
73787fef653a58995e898785af732a4c 6164 python optional
python-authlib_1.9.1-1.debian.tar.xz
2828a4aefb24eced05df0f44ae4a11b4 7342 python optional
python-authlib_1.9.1-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCauG27xQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2PzHAP9hSFGQMol+fc/PsedC1UcLk5kRVIW9
EihR4hnqbuqejgD/SM0Vr1lnQ6p5aswzP0oeXT/RSxpdEqbWjyeUNHWgQAQ=
=8vRj
-----END PGP SIGNATURE-----
pgpIMgEJUDoRD.pgp
Description: PGP signature
--- End Message ---