cve.bz

CVE-2026-114616 authlib authlib: Improper Authentication

9.1 criticalExploit referenceEPSS 0.3%Fix available

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

On this page
Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.1, Authlib's OctKey.import_key() and HMAC signing and verification path accept zero-length key material. If an application's secret lookup can return an empty string or empty bytes, a remote attacker can compute the deterministic HS256, HS384, or HS512 signature for arbitrary token claims and have Authlib treat the token as authentic. This issue is fixed in version 1.9.1.

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.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-30. 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-287 Improper Authentication
CWE-326 Inadequate Encryption Strength
CWE-1391 Use of Weak Credentials
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication 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-114616 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114616?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114616?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-114616 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:authlibbefore 1.9.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8m4g-j4wp-wgcgPyPIauthlib<1.9.11.9.1
PYSEC-2026-4356PyPIauthlib<1.9.11.9.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-authlibno fix listedDEBIAN-CVE-2026-114616
Debian14python-authlib1.9.1-1DEBIAN-CVE-2026-114616
Ubuntu26.10, Pro:22.04:LTS, Pro:24.04:LTS and 1 morepython-authlibno fix listedUBUNTU-CVE-2026-114616
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 successful exploitation enables remote unauthenticated token forgery and full authentication bypass, though the risk is constrained by the prerequisite that the consuming service must resolve HMAC secrets to empty values. In standard Red Hat deployments, underlying services and containerized offerings enforce or dynamically provision defined secret keys, substantially reducing exposure under default configurations. However, if an application environment fails to supply a secret or allows key lookups to return blank values, external actors can generate predictable signatures and gain unauthorized access.

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-114616.

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-192 Protocol Analysis Likelihood: Low · Severity: Low
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data 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-287.

References

Check your stackJSON