Is CVE-2026-114615 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114615 being exploited in the wild.

How severe is CVE-2026-114615?

High severity, with a CVSS score of 7.4, published 22 October 2026.

Which products and versions are affected?

Authlib 1.3.1 to 1.8.x; authlib (PyPI) >= 1.3.1, <= 1.8.0, ECOSYSTEM:introduced=1.3.1,fixed=1.9.0.

Is there a fix for CVE-2026-114615?

Yes. authlib (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114615 attacked?

It is attacked over the network.

Am I affected by CVE-2026-114615?

Check whether you run Authlib or authlib (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114615: Authlib HMAC secret confusion in JWT verification

Q: Is there a fix for CVE-2026-114615?

Yes. authlib (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-114615 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-114615?

Check whether you run Authlib or authlib (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114615 · Severity: high · CVSS 7.4 · Published 2026-10-22

Authlib is a Python library used to build OAuth and OpenID Connect servers. The library fails to properly validate cryptographic keys when verifying JSON Web Tokens (JWTs), allowing attackers to use public key material as an HMAC secret to forge authentication tokens with arbitrary claims. This can lead to account takeover and unauthorized access to protected resources.

Technologies: Authlib, authlib (PyPI). Vendors: Authlib, PyPI.

Quick answers

Is CVE-2026-114615 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114615 being exploited in the wild.
How severe is CVE-2026-114615?: High severity, with a CVSS score of 7.4, published 22 October 2026.
Which products and versions are affected?: Authlib 1.3.1 to 1.8.x; authlib (PyPI) >= 1.3.1, <= 1.8.0, ECOSYSTEM:introduced=1.3.1,fixed=1.9.0.
Is there a fix for CVE-2026-114615?: Yes. authlib (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114615 attacked?: It is attacked over the network.
Am I affected by CVE-2026-114615?: Check whether you run Authlib or authlib (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

authlib (PyPI): upgrade to 1.9.0 or later
```
pip install "authlib>=1.9.0"
```

Technical details

OctKey.import_key() in authlib/jose/rfc7518/oct_key.py fails to reject asymmetric key material prefixed with whitespace, comments, or byte-order marks, while the PEM loader accepts these prefixes. In mixed algorithm registries, an attacker with knowledge of public key bytes can exploit this to use them as an HMAC-SHA256 secret for JWT forgery. This bypasses the remediation for CVE-2024-37568 and affects deployments configured for both symmetric and asymmetric verification.

Affected products

Authlib Authlib 1.3.1 to 1.8.x

Identifiers

CVE-2026-114615
GHSA-7vr2-2fgp-9w7p
PYSEC-2026-4355

Timeline

2026-10-22: disclosed
2026-10-08: patched: Fix merged in commit e3bd41cb29dcfee434453b135ffb487884baeedf

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.