1-minute read
What a defender needs to know
Authlib’s JSON Web Signature handling accepts a general-JSON JWS with an empty signatures array as successfully verified, according to CERT/CC’s September 28 vulnerability note. The defect affects Authlib through 1.7.2 and carries the identifier CVE-2026-96760. The verification routine begins in a successful state; with no signatures to iterate over, it returns that state without a cryptographic check. A Python service that trusts the returned payload for identity, authorization, inter-service message integrity, or signed configuration can accept forged content without an attacker holding a signing key.
Find JsonWebSignature.deserialize_json, jws.deserialize_json, and jws.deserialize call sites and trace untrusted general-JSON JWS input to the decisions they control. Record the deployed Authlib version at each exposed service. Add an application-side guard before deserialization to reject an empty signatures list, then run a safe regression fixture: the empty-list object must be rejected before any payload is trusted, while legitimate signed-message fixtures continue to pass. This guard addresses the described path; a future fixed release requires its own version and regression check.
PyPI lists 1.8.0, uploaded before the CERT/CC note; CERT/CC reported no official patch at publication. Treat that release as an unconfirmed fix and keep the guard until a maintainer documents remediation. Scope exposure by tracing each JWS deserialization call to its use of the returned payload.