External risk intelligence

Authlib Key Import Vulnerability Allows Token Forgery

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-114615

Authlib is a library used to build OAuth and OpenID Connect servers. Because these servers function as identity portals and public-facing authentication endpoints, they are designed to be accessible via the internet in normal deployments to facilitate authentication flows for users and services.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in the Authlib Python library, which is used for building OAuth and Open ID Connect servers. The issue allows an unauthenticated attacker to forge security tokens, potentially leading to unauthorized access or claims. The main concern is confirming relevance and exposure to this type of authentication infrastructure.

  • Security flaw allows attackers to forge tokens.
  • Critical vulnerability in common authentication servers.
  • Confirm if your authentication infrastructure is affected.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could forge secure tokens if a server uses a vulnerable version of the Authlib library. This is possible when the library is configured to accept PEM-formatted keys and the attacker knows the specific public key bytes used by the server. By providing these known public key bytes as an HMAC secret, the attacker can bypass security checks and create tokens with any desired claims.

  • Publicly accessible authentication endpoint required.
  • Attacker provides known public key bytes as secret.
  • Forged tokens can grant unauthorized access.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker could forge authentication tokens with arbitrary claims by exploiting how Authlib processes asymmetric keys. This is possible when using mixed algorithms with PEM or certificate bytes that contain leading whitespace, comments, or a byte-order mark, and when verification is configured with such prefixed keys. This bypasses a previous security fix.

  • Forged tokens with arbitrary claims.
  • Using public-key bytes as HMAC secrets.
  • Unauthorized access or identity claims.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Platform or Application Security teams are likely responsible for addressing this vulnerability, given Authlib's role in building OAuth and OpenID Connect servers. The first step is to identify all deployments of Authlib, confirm their reachability and criticality, and locate the accountable owner before planning remediation.

  • Ownership: Platform or Application Security teams.
  • Verify first: Asset inventory and exposure.
  • Action: Coordinate vendor updates or temporary risk reduction.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Authlib?

Authlib is a Python library that provides the core tools needed to build OAuth and OpenID Connect servers. It is used by developers to manage identity verification and secure authentication processes, effectively acting as the engine that handles how services issue and validate the digital credentials that control access.

What does CVE-2026-114615 mean for token security?

This vulnerability is an improper validation issue, classified as CWE-184 and CWE-347. It creates a path for attackers to trick the library into treating a public key as a secret HMAC key. This allows the creation of forged security tokens, enabling an attacker to bypass authentication and claim any identity or authorization level they choose.

How can an attacker trigger this vulnerability?

An attacker needs to provide specific public key bytes that the server already uses. The bug is triggered when the library mistakenly processes PEM-formatted keys that contain leading whitespace or comments. Importantly, standard deployments not using this specific mixed-algorithm configuration or those without these character prefixes do not trigger this bypass.

Why is this a concern for internet-facing systems?

According to Halo Surface Signal, Authlib is used to build identity portals and authentication endpoints, which are frequently exposed to the internet. Because these services are designed to accept incoming requests from users and other services, they are highly accessible, making this vulnerability a priority for any public-facing login infrastructure.

How do I secure my environment against this CVE?

The primary response is to update the Authlib library to version 1.9.0 or later, which resolves the processing error. Start by auditing your applications to identify where Authlib is integrated, confirm if your specific key configuration is in use, and prioritize updating these identity services to prevent potential token forgery.

References