cve.bz

CVE-2026-114617 authlib authlib: Authentication Bypass by Capture-replay

4.2 mediumExploit referenceEPSS 0.3%Fix available

Medium (4.2) in authlib authlib. EPSS 0.3% 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. Prior to 1.9.0, OpenIDMixin.parse_id_token() reads the nonce_supported decision from the untrusted ID token being validated and sets the expected nonce to null when that claim is the JSON boolean false. In implicit and hybrid relying parties, or applications that directly accept externally supplied ID tokens, an attacker with a captured validly signed token can bypass the nonce-to-session binding and replay the victim's token into an attacker-controlled session. Plain authorization code flow is not affected, and the token must still pass signature, issuer, and audience validation. OpenIDMixin.parse_id_token() trusts nonce_supported in both authlib/integrations/base_client/sync_openid.py and authlib/integrations/base_client/async_openid.py to disable the expected nonce. This issue is fixed in version 1.9.0.

Severity

CVSS 3.1

4.2 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 19th 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: partial, assessed 2026-10-23. 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-294 Authentication Bypass by Capture-replay
CWE-807 Reliance on Untrusted Inputs in a Security Decision
OWASP Top 10
A06:2025 Insecure Design, 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-114617 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114617?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114617?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-114617 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.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c5mf-xmp2-59rcPyPIauthlib<1.9.01.9.0
PYSEC-2026-4357PyPIauthlib<1.9.01.9.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-authlibno fix listedDEBIAN-CVE-2026-114617
Debian14python-authlib1.9.1-1DEBIAN-CVE-2026-114617
Ubuntu26.10, Pro:22.04:LTS, Pro:24.04:LTS and 1 morepython-authlibno fix listedUBUNTU-CVE-2026-114617
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 Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because successful exploitation requires specific environmental prerequisites, including the interception of a legitimately signed token and target applications utilizing implicit or hybrid identity flows. Standard authorization code flows, which represent the default and recommended authentication pattern across Red Hat deployments, are not susceptible to this replay weakness. Furthermore, any submitted token must still satisfy cryptographic signature, audience, and issuer validations to be processed.

ProductPackageStateAdvisory
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Out of support scope
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Fix deferred
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Fix deferred
OpenShift Lightspeedopenshift-lightspeed/lightspeed-agentic-sandbox-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-chatbot-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-chatbot-rhel9Fix deferred
Red Hat Enterprise Linux command line assistantrhel-cla/rhel-knowledge-bridge-rhel10Fix deferred
Red Hat OpenShift Virtualization 4container-native-virtualization/ocp-virt-validation-checkup-rhel9Fix deferred
Red Hat Quay 3quay/quay-rhel8Out of support scope
Red Hat Quay 3quay/quay-rhel9Out of support scope
Red Hat Satellite 6satellite/foreman-mcp-server-rhel9Fix deferred

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

Attack patterns (CAPEC)

  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-509 Kerberoasting Severity: High
  • CAPEC-555 Remote Services with Stolen Credentials Severity: Very High
  • CAPEC-561 Windows Admin Shares with Stolen Credentials
  • CAPEC-644 Use of Captured Hashes (Pass The Hash) Likelihood: Medium · Severity: High
  • CAPEC-645 Use of Captured Tickets (Pass The Ticket) Likelihood: Low · Severity: High
  • CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
  • CAPEC-701 Browser in the Middle (BiTM) Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON