CVE-2026-114615 json
Authlib incomplete algorithm-confusion fix permits HMAC forgery with prefixed public keys
published 18d ago modified 10d ago also EUVD-2026-108514 , GHSA-7vr2-2fgp-9w7p , PYSEC-2026-4355
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi authlib 1.9.0
- authlib authlib 1.9.0
- python-authlib Debian 14 1.9.1-1
debian advisories DEBIAN-CVE-2026-114615
- python-Authlib openSUSE Tumbleweed 1.9.1-1.1
opensuse advisories openSUSE-SU-2026:12390-1
- github.com/authlib/authlib@e3bd41c commit
- github.com/authlib/authlib#945 pull request
- github.com/authlib/authlib/releases/tag/v1.9.0 release
Is CVE-2026-114615 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-114615 updated cvss 7.4
authlib: Authlib: Authentication bypass via improper asymmetric key validation
-
Red Hat Exploit Intelligence exploit-intelligence/vulnerability-analysis-rhel9 Red Hat Lightspeed Core lightspeed-core/lightspeed-stack-rhel9 Red Hat Migration Toolkit for Applications 8 mta/mta-solution-server-rhel9affected: workaround, no fix available
-
Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-agentic-sandbox-rhel9affected: workaround, no fix planned “Will not fix”
-
Red Hat Ansible Automation Platform 2 ansible-automation-platform-26/lightspeed-chatbot-rhel9, ansible-automation-platform-27/lightspeed-chatbot-rhel9 Red Hat OpenShift Virtualization 4 container-native-virtualization/ocp-virt-validation-checkup-rhel9 Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9affected: workaround, no fix available
-
Red Hat Satellite 6.18 satellite/foreman-mcp-server-rhel9 1793272276fixed: vendor fix RHSA-2026:92667
-
Red Hat Satellite 6.19 satellite/foreman-mcp-server-rhel9 1793272279fixed: vendor fix RHSA-2026:92666
-
Red Hat Enterprise Linux command line assistant rhel-cla/rhel-knowledge-bridge-rhel10not affected: vulnerable code not in execute path
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 11d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/authlib/authlib/security/advisories/GHSA-7vr2-2fgp-9w7p referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | authlib | >=1.3.1, <1.9.0 |
1.9.0 |
Affected products
- authlib authlib
Classification
References
-
github.com
/authlib/authlib/pull/945
web, patch
-
github.com
/authlib/authlib/commit/e3bd41cb29dcfee434453b135ffb487884baeedf
web, patch
-
github.com
/authlib/authlib/security/advisories/GHSA-7vr2-2fgp-9w7p
exploit, web, mitigation, vendor-advisory, evidence
-
github.com
/authlib/authlib/releases/tag/v1.9.0
web, release-notes, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-114615
advisory
-
github.com
/authlib/authlib
package
Sources
- CVE List CVE-2026-114615
- GitHub Advisory GHSA-7vr2-2fgp-9w7p
- NVD CVE-2026-114615
- OSV PYSEC-2026-4355
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.