Red Hat Security Advisory: RHTAS 1.5.1 - Release of Model Transparency 1.0.6
Affects Red HatSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade Red Hat pyjwt to 2.14.0 as a priority.
Data as of 6 Nov 2026, 05:52 UTC
- Patch
- Available – fixed in 2.14.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 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 5 Nov 2026.
What to do
Upgrade pyjwt to 2.14.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jpadillapyjwt | Affected
| Fixed in
|
PyPIpyjwtpkg:pypi/pyjwtOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Currently, there is no mitigation available that meets Red Hat Product Security criteria for ease of use, applicability, or stability. Deployments should avoid configurations that accept both symmetric and asymmetric signing algorithms simultaneously. Enforcing a single algorithm type or using JSON Web Key sets for token validation prevents exploitation of this vulnerability.
Description
A critical vulnerability exists in PyJWT, a library used for JSON Web Token handling, where improper validation of public keys allows an attacker to forge valid authentication tokens. This occurs when applications accept both symmetric and asymmetric signing algorithms, causing the library to misinterpret asymmetric public keys as symmetric secrets. This flaw enables unauthenticated remote attackers to bypass authentication without the private key. Deployments that enforce a single algorithm type or use JSON Web Key sets are not affected.
References
- access.redhat.com/errata/RHSA-2026:95261 (opens in a new tab)
- access.redhat.com/documentation/en-us/red_hat_trusted_artifact_signer/1.5 (opens in a new tab)
- access.redhat.com/documentation/en-us/red_hat_trusted_artifact_signer/1.5/html-single/release_notes/index (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-102268 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-102271 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-102272 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-102273 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-114605 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-119194 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-119195 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-119196 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_95261.json (opens in a new tab)