cve.bz

CVE-2026-114615 authlib authlib: Incomplete List of Disallowed Inputs

9.1 criticalExploit referenceEPSS 0.2%Fix available

Critical (9.1) in authlib authlib. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in authlib 1.9.0.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-184 Incomplete List of Disallowed Inputs
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-114615 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114615?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114615?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114615 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
authlib:authlibfrom 1.3.1 before 1.9.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7vr2-2fgp-9w7pPyPIauthlib>=1.3.1 <1.9.01.9.0
PYSEC-2026-4355PyPIauthlib>=1.3.1 <1.9.01.9.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-authlibno fix listedDEBIAN-CVE-2026-114615
Debian14python-authlib1.9.1-1DEBIAN-CVE-2026-114615
Ubuntu26.10, Pro:22.04:LTS, Pro:24.04:LTS and 1 morepython-authlibno fix listedUBUNTU-CVE-2026-114615
openSUSETumbleweedpython-Authlib1.9.1-1.1openSUSE-SU-2026:12390-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an unauthenticated remote attacker could forge cryptographic tokens and bypass authentication, leading to unauthorized access. The issue stems from incomplete validation of asymmetric key prefixes, which permits public keys with non-canonical formatting to be treated as symmetric secrets when mixed algorithm registries are enabled. In Red Hat environments, overall exposure is constrained to services that permit dynamic algorithm selection alongside non-stripped public key configurations.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Satellite 6.18satellite/foreman-mcp-server-rhel9:1793272276Fixed 2026-10-29RHSA-2026:92667
Red Hat Satellite 6.19satellite/foreman-mcp-server-rhel9:1793272279Fixed 2026-10-29RHSA-2026:92666
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Affected
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Affected
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-agentic-sandbox-rhel9Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-chatbot-rhel9Affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-chatbot-rhel9Affected
Red Hat Enterprise Linux command line assistantrhel-cla/rhel-knowledge-bridge-rhel10Affected
Red Hat OpenShift Virtualization 4container-native-virtualization/ocp-virt-validation-checkup-rhel9Affected
Red Hat Quay 3quay/quay-rhel8Affected
Red Hat Quay 3quay/quay-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-114615.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-184.

References

Check your stackJSON