Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-114615Published 2026-10-22

CVE-2026-114615 — authlib

high

As of 2026-10-22, CVE-2026-114615 is a HIGH-severity vulnerability in authlib, CVSS v3.1 7.4, EPSS 0.1% (2.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-114615 as of 2026-10-22; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
7.4/10High
EPSS
0.1%Higher than 2.1% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.8/10Threadlinqs triage score
Published
CVSS v3.1 7.4 (HIGH) · EPSS 0.1% (higher than 2.1% of all scored CVEs) · Priority 3.8/10 · Published 2026-10-22

Last updated:

What is CVE-2026-114615?

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.

The record classifies CVE-2026-114615 under weakness classes CWE-184, CWE-347. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 28 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.4 — HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 2.1% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-22

Is CVE-2026-114615 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-114615

No vendor patch reference has been recorded for CVE-2026-114615 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-114615

No threat campaign in the Threadlinqs corpus currently references CVE-2026-114615, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references