Authlib signature verification bypass in JWS deserialization
Free public brief. The indicators, the detections with Splunk and KQL already written, and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Authlib up to 1.7.2 accepts empty JWS signature arrays, allowing attackers to forge authentication tokens and bypass signature verification without key material.
Authlib, a widely-used Python library for OAuth, OpenID Connect, and JWT/JWS/JWE handling, contains a critical signature-verification bypass in its JSON Web Signature deserialization function. The JsonWebSignature.deserialize_json() method incorrectly treats JWS objects with empty "signatures" arrays as validly signed, allowing attackers to supply forged payloads without any cryptographic key material. Both JSON and compact JWS deserialization methods are affected. An attacker can exploit this to forge authentication tokens with arbitrary claims (identity, privilege escalation), inject malicious messages between microservices, forge authorization claims, or bypass integrity checks in systems relying on JWS verification. The vulnerability has been reported but no official patch was available at the time of the CERT/CC advisory publication. Affected organizations should monitor the Authlib GitHub repository for updates and upgrade immediately once a fix is released.
Mentioned in this report
Source reporting: https://kb.cert.org/vuls/id/762428
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections with the Splunk SPL and Microsoft KQL already written, the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 11,192 reports from 149 sources, 2,695 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs