CyberSecBulletin
CVE-2026-27962NVD status: Modified

authlib: Improper Verification of Cryptographic Signature

CVE-2026-27962 is a critical-severity improper verification of cryptographic signature vulnerability in authlib, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected authlib versions: < 1.6.9. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.61% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of authlib you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Authlibauthlib< 1.6.9Not stated
Red HatRed Hat Quay 3.10Not specified in the recordNot stated
Red HatRed Hat Quay 3.14Not specified in the recordNot stated
Red HatRed Hat Quay 3.15Not specified in the recordNot stated
Red HatRed Hat Quay 3.16Not specified in the recordNot stated
Red HatRed Hat Quay 3.18Not specified in the recordNot stated
Red HatLightspeed CoreNot specified in the recordNot stated
Red HatRed Hat Ansible Automation Platform 2Not specified in the recordNot stated
Red HatRed Hat OpenShift AI (RHOAI)Not specified in the recordNot stated
Red HatRed Hat Satellite 6Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (github.com).

Scoring systemScoreSeverityScored by
CVSS 3.19.1CriticalCNA (github.com)
CVSS 3.19.1CriticalCNA

Official description

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.9, a JWK Header Injection vulnerability in authlib's JWS implementation allows an unauthenticated attacker to forge arbitrary JWT tokens that pass signature verification. When key=None is passed to any JWS deserialization function, the library extracts and uses the cryptographic key embedded in the attacker-controlled JWT jwk header field. An attacker can sign a token with their own private key, embed the matching public key in the header, and have the server accept the forged token as cryptographically valid — bypassing authentication and authorization entirely. This issue has been patched in version 1.6.9.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Verification of Cryptographic Signature

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

More Improper Verification of Cryptographic Signature vulnerabilities (CWE-347)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in authlib

All authlib vulnerabilities

Recent Improper Verification of Cryptographic Signature vulnerabilities

Spotted an error? Tell us.