Official source article: GitHub GHSA-GVP8-978C-RX2Q ↗. Check the applicable product and release in the original source.
6.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 237 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Published severityMedium→Operational priority:High, raised one band.upgradedsince 30 Sep 2026
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.24% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs jpadilla pyjwt and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Cross-source reconciliation
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 237 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Red Hat Product Security: 237 affected or under-investigation product states without a fixed product state in the same current advisory
Distribution package intelligence
Release-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
5 package states
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Distribution release
Source package
Vendor state
Fixed version
Evidence
Debian trixietrixie · source
pyjwt
Not affectedDebian marks this release not affected (fixed-version marker 0).
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
Ecosystem and package
Affected range
First fixed version
Evidence
PyPIpyjwt
ECOSYSTEM: introduced 2.11.0; last affected 2.13.0
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
python-PyJWT as component of SUSE Linux Enterprise Server 16.0
python313-PyJWT as component of SUSE Linux Enterprise Server 16.0
python-PyJWT as component of SUSE Linux Enterprise Server 16.1
python313-PyJWT as component of SUSE Linux Enterprise Server 16.1
python-PyJWT as component of SUSE Linux Enterprise Server for SAP applications 16.0
python313-PyJWT as component of SUSE Linux Enterprise Server for SAP applications 16.0
python-PyJWT as component of SUSE Linux Enterprise Server for SAP applications 16.1
python313-PyJWT as component of SUSE Linux Enterprise Server for SAP applications 16.1
python-PyJWT as component of SUSE Linux Micro 6.1
python311-PyJWT as component of SUSE Linux Micro 6.1
python-PyJWT as component of SUSE Linux Micro 6.2
python313-PyJWT as component of SUSE Linux Micro 6.2
Summary
PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-103001 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypyjwt: pyjwt: Token validation bypass via options dictionary mutation
237 known affected
The vendor explicitly identifies these products as affected by this CVE.
ansible-automation-platform/automation-orchestrator-backend-rhel9 as a component of Ansible Automation Orchestrator 2026
openshift-sandboxed-containers/osc-podvm-builder-rhel9 as a component of Confidential Compute Attestation
workload-availability/fence-agents-remediation-rhel9-operator as a component of Fence Agents Remediation Operator
lightspeed-core/lightspeed-stack-rhel9 as a component of Lightspeed Core
lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core
lightspeed-core/rag-tool-cuda-12.9-rhel9 as a component of Lightspeed Core
mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8
openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed
openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed
openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed
rhaii/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server
rhaii/vllm-cuda-rhel9 as a component of Red Hat AI Inference Server
Summary
A flaw was found in pyjwt. This vulnerability allows a remote attacker to bypass token validation checks when an application reuses an options configuration across multiple token decoding requests. Because the library unintentionally modifies the caller's shared configuration dictionary when signature verification is disabled, subsequent token verifications may retain disabled claim checks. As a result, an attacker could supply an expired or otherwise invalid JSON Web Token (JWT) that the application accepts as valid.
Remediation
Until a fixed PyJWT version is available, create a new options dictionary for each decode() or decode_complete() call. Do not reuse a mutable options dictionary between calls with different verification settings.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-90388
No EUVD known-exploited evidence
PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
6.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 237 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product
01
What, why and how
PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
What
PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
Why
The product does not properly protect an assumed-immutable element from being modified by an attacker.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
Why
The product does not properly protect an assumed-immutable element from being modified by an attacker.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
a network path → Modification of Assumed-Immutable Data (MAID) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-471: Modification of Assumed-Immutable Data (MAID). The product does not properly protect an assumed-immutable element from being modified by an attacker.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-90388Official EUVD mapping
PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.
Official EUVD record ↗Cyber Security Agency of Singapore · English · CSA-SB-20261007Security Bulletin 7 Oct 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 7 Oct 2026, published on 7 October 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 30 Sept 2026 · Last source change 5 Oct 2026, 23:47 UTC · CWE-471 · Modification of Assumed-Immutable Data (MAID)
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-10-01
European sourceENISA EUVD · EUVD-2026-90388
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
After
ansible-automation-platform/automation-orchestrator-backend-rhel9 as a component of Ansible Automation Orchestrator 2026; openshift-sandboxed-containers/osc-podvm-builder-rhel9 as a component of Confidential Compute Attestation; workload-availability/fence-agents-remediation-rhel9-operator as a component of Fence Agents Remediation Operator; lightspeed-core/lightspeed-stack-rhel9 as a component of Lightspeed Core; lightspeed-core/rag-tool-cpu-rhel9 as a component of Lightspeed Core; lightspeed-core/rag-tool-cuda-12.9-rhel9 as a component of Lightspeed Core; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed; rhaii/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server; rhaii/vllm-cuda-rhel9 as a component of Red Hat AI Inference Server; rhaii/vllm-gaudi-rhel9 as a component of Red Hat AI Inference Server; rhaii/vllm-neuron-rhel9 as a component of Red Hat AI Inference Server; rhaii/vllm-rocm-rhel9 as a component of Red Hat AI Inference Server; rhaii/vllm-spyre-rhel9 as a component of Red Hat AI Inference Server; rhaii/vllm-tpu-rhel9 as a component of Red Hat AI Inference Server; rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server; rhaiis/vllm-cuda-rhel9 as a component of Red Hat AI Inference Server; rhaiis/vllm-rocm-rhel9 as a component of Red Hat AI Inference Server; rhaiis/vllm-tpu-rhel9 as a component of Red Hat AI Inference Server; ansible-automation-platform-24/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/eda-controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/hub-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/lightspeed-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/eda-controller-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; and 207 more
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.