CVE-2026-39373VulnerabilityPublished 19 May 2026Updated 31 Oct 2026

Red Hat Security Advisory: python-jwcrypto security update

Affects Red Hat python-jwcryptoSource GCVE Database

Compare

Authoritative record:CVE-2026-39373· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade Red Hat jwcrypto to 1.5.7 when convenient.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.5.7

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jwcrypto to 1.5.7.

Affected software

Product	Affected	Fixed in
latchsetjwcrypto	Affected <1.5.7	Fixed in 1.5.7
PyPIjwcrypto`pkg:pypi/jwcrypto`Other threats	Affected <1.5.7	Fixed in 1.5.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released an official security update for python-jwcrypto in Red Hat Enterprise Linux 10 and its extended support versions. Applying the updated packages (python-jwcrypto-1.5.6-5.el10_2) will remediate the vulnerability. Users should follow Red Hat's update instructions at https://access.redhat.com/articles/11258 to apply the patch. No additional mitigation steps are indicated by the vendor.

Description

A low severity security vulnerability (CVE-2026-39373) affecting the python-jwcrypto package in Red Hat Enterprise Linux 10 has been addressed. The issue involves memory exhaustion caused by crafted compressed JSON Web Encryption (JWE) tokens. Red Hat has released an update for python-jwcrypto to fix this vulnerability. The advisory covers multiple architectures including x86_64, s390x, ppc64le, and aarch64. No public exploits or in-the-wild exploitation have been reported. The update is available and should be applied to affected systems.

Impact

The vulnerability can cause memory exhaustion on systems processing maliciously crafted compressed JWE tokens using python-jwcrypto. This may degrade system performance or cause denial of service conditions. The impact is rated low by Red Hat, indicating limited risk or difficulty in exploitation. There are no known exploits in the wild.

Summary

The vulnerability CVE-2026-39373 in python-jwcrypto involves memory exhaustion triggered by specially crafted compressed JWE tokens. This can lead to resource exhaustion on affected systems running Red Hat Enterprise Linux 10. The issue is rated as low severity by Red Hat Product Security. A security update has been issued to address this flaw, with updated python-jwcrypto packages provided for various supported architectures. No CVSS score is provided, and no exploitation in the wild has been observed. The advisory references Red Hat's official errata RHSA-2026:19042 and provides package updates for Red Hat Enterprise Linux 10 and its extended support versions.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2026, 17:50 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats