cve.bz

CVE-2026-49852 authlib joserfc: Improper Authentication

8.7 highEPSS 0.2%Fix available

High (8.7) in authlib joserfc. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in joserfc 1.6.8.

On this page
joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. Prior to 1.6.8, joserfc.jwt.decode accepts attacker-forged HMAC-signed tokens when the caller-supplied verification key is the empty string or None, because HMACAlgorithm.sign and HMACAlgorithm.verify in src/joserfc/_rfc7518/jws_algs.py pass the output of OctKey.get_op_key(...) to hmac.new(...) and OctKey.import_key in src/joserfc/_rfc7518/oct_key.py only emits a SecurityWarning for keys shorter than 14 bytes without rejecting zero-length input. This issue is fixed in version 1.6.8.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-07-20. 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
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-49852 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49852?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49852?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-49852 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 CNA's record in the CVE List.

ProductAffected
authlib joserfc< 1.6.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gg9x-qcx2-xmrhPyPIjoserfc<1.6.81.6.8
PYSEC-2026-2528PyPIjoserfc<1.6.81.6.8

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13joserfcno fix listedDEBIAN-CVE-2026-49852
Debian14joserfc1.6.8-1DEBIAN-CVE-2026-49852
Ubuntu26.04:LTSjoserfcno fix listedUBUNTU-CVE-2026-49852
Red Hathummingbird:1jaeger0:2.19.0-1.2.hum1RHSA-2026:42045
openSUSELeap 16.0python-joserfc1.1.0-bp160.3.1openSUSE-SU-2026:21263-1
openSUSETumbleweedpython-joserfc1.7.2-2.1openSUSE-SU-2026:11183-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

CVE-2026-49852 is an integrity/authentication bypass in the joserfc Python library (CWE-347): joserfc.jwt.decode accepts attacker-forged HMAC-signed tokens when the verification key is an empty string or None, allowing an attacker to forge valid-looking JWTs. It is fixed in joserfc 1.6.8. Red Hat rates this Important, consistent with the upstream/CVEORG assessment.

joserfc is bundled by a number of Red Hat product and services container images. Version triage against the fixed version (1.6.8) shows only two shipping components carried a vulnerable joserfc (1.6.5) and are marked Affected: OpenShift Virtualization (CNV) 4.22 (ocp-virt-validation-checkup) and OpenShift Dedicated / hosted control planes (ask-sre). All other Red Hat components that bundle joserfc ship 1.6.8 or later (1.7.1-1.7.4) and are Not Affected because the vulnerable code is not present. The Red Hat Hardened Images (Hummingbird) jaeger package shipped an affected joserfc (1.6.7) and has already been remediated (rebuilt with joserfc 1.7.1, HUM-4648).

Red Hat's mitigation

This flaw is only exploitable when an application invokes joserfc.jwt.decode with an empty-string or None verification key. Ensuring a valid, non-empty key is always supplied to JWT verification prevents exploitation. Upgrading joserfc to 1.6.8 or later fully remediates the flaw regardless of how the verification key is supplied.

ProductPackageStateAdvisory
Red Hat Hardened Imagesjaeger-main-2.19.0-1.2.hum1Fixed 2026-07-20RHSA-2026:42045
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Not affected
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-agentic-sandbox-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-chatbot-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-chatbot-rhel9Not affected
Red Hat Enterprise Linux command line assistantrhel-cla/rhel-knowledge-bridge-rhel10Not affected
Red Hat OpenShift Virtualization 4container-native-virtualization/ocp-virt-validation-checkup-rhel9Not affected
Red Hat Satellite 6satellite/foreman-mcp-server-rhel9Not affected

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

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