BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-32597High confidence

PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)

jpadilla · pyjwt

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivepyjwtVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.2.7.0-1ubuntu0.1Canonical record ↗Source updated 11 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-32597 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypyjwt: PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)
12 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed
  • openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed
  • openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed
  • rhaiis/vllm-cpu-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-25/lightspeed-chatbot-rhel8 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • rhoai/odh-llama-stack-core-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • satellite/foreman-mcp-server-rhel9 as a component of Red Hat Satellite 6
  • rhtas/segment-reporting-rhel9 as a component of Red Hat Trusted Artifact Signer
Summary
A missing verification step has been discovered in PyJWT. PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC.
Remediation
For details on how to apply this update, refer to Ansible Automation Platform documentation.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-11728

No EUVD known-exploited evidence

PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

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
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

What

PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

Why

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

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 JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

Why

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

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

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Insufficient Verification of Data Authenticity → 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
Low: no specialised conditions are recorded
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-345 ↗

CWE-345: Insufficient Verification of Data Authenticity. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

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:L/PR:N/UI:N/S:U/C:N/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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.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.CNoneConfidentiality impact: No direct loss is represented by this metric.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.
NetworkUnauthenticatedCWE-345Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-11728Official EUVD mapping

PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

Official EUVD record
BSI · German · WID-SEC-2026-3046IBM Concert: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory
BSI · German · WID-SEC-2026-2933Splunk SOAR: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um beliebigen Programmcode auszuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1056Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-31789 Référence CVE CVE-2026-31790 https://www.cve.org/CVERecord?id=CVE-2026-31790 Référence CVE CVE-2026-31898 https://www.cve.org/CVERecord?id=CVE-2026-31898 Référence CVE CVE-2026-31938 https://www.cve.org/CVERecord?id=CVE-2026-31938 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-32647 https://www.cve.org/CVERecord?id=CVE-2026-32647 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33810 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0667Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-29786 Référence CVE CVE-2026-30922 https://www.cve.org/CVERecord?id=CVE-2026-30922 Référence CVE CVE-2026-30951 https://www.cve.org/CVERecord?id=CVE-2026-30951 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-31808 https://www.cve.org/CVERecord?id=CVE-2026-31808 Référence CVE CVE-2026-31988 https://www.cve.org/CVERecord?id=CVE-2026-31988 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-32874 https://www.cve.org/CVERecord?id=CVE-2026-32874 Référence CVE CVE-2026-32875 https://www.cve.org/CVERecord?id=CVE-2026-32875 Référence CVE CVE-2026-33036 https://www.cve.org/CVERecord?id=CVE-2026-33036 Référence CVE CVE-2026-3304 https://www.cve.org/CVERecord?id=CVE-2026-3304 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33349 https://www.cve.org/CVERecord?id=CVE-2026-33349 Référence CVE CVE-2026-33412 https://www.cve.org/CVERecord?id=CVE-2026-33412 Référence CVE CVE-2026-33916 https://www.cve.org/CVERecord?id=CV

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0641Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-26996 Référence CVE CVE-2026-27142 https://www.cve.org/CVERecord?id=CVE-2026-27142 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-29045 https://www.cve.org/CVERecord?id=CVE-2026-29045 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-29087 https://www.cve.org/CVERecord?id=CVE-2026-29087 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-35554 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2026-28419 Référence CVE CVE-2026-28420 https://www.cve.org/CVERecord?id=CVE-2026-28420 Référence CVE CVE-2026-28421 https://www.cve.org/CVERecord?id=CVE-2026-28421 Référence CVE CVE-2026-28422 https://www.cve.org/CVERecord?id=CVE-2026-28422 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-3195 https://www.cve.org/CVERecord?id=CVE-2026-3195 Référence CVE CVE-2026-3196 https://www.cve.org/CVERecord?id=CVE-2026-3196 Référence CVE CVE-2026-32249 https://www.cve.org/CVERecord?id=CVE-2026-32249 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-3441 https://www.cve.org/CVERecord?id=CVE-2026-3441 Référence CVE CVE-2026-3442 https://www.cve.org/CVERecord?id=CVE-2026-3442 Référence CVE CVE-2026-3497 https://www.cve.org/CVERecord?id=CVE-2026-3497 Référence CVE CVE-2026-3731 https://www.cve.org/CVERecord?id=CVE-2026-3731 Référence CVE CVE-2026-3783 https://www.cve.org/CVERecord?id=CVE-2026-3783 Référence CVE CVE-2026-3784 https://www.cve.org/CVERecord?id=CVE-2026-3784 Gestion détaillée du document le 20 mars 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Conta

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2026-28419 Référence CVE CVE-2026-28420 https://www.cve.org/CVERecord?id=CVE-2026-28420 Référence CVE CVE-2026-28421 https://www.cve.org/CVERecord?id=CVE-2026-28421 Référence CVE CVE-2026-28422 https://www.cve.org/CVERecord?id=CVE-2026-28422 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-3195 https://www.cve.org/CVERecord?id=CVE-2026-3195 Référence CVE CVE-2026-3196 https://www.cve.org/CVERecord?id=CVE-2026-3196 Référence CVE CVE-2026-32249 https://www.cve.org/CVERecord?id=CVE-2026-32249 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-3441 https://www.cve.org/CVERecord?id=CVE-2026-3441 Référence CVE CVE-2026-3442 https://www.cve.org/CVERecord?id=CVE-2026-3442 Référence CVE CVE-2026-3497 https://www.cve.org/CVERecord?id=CVE-2026-3497 Référence CVE CVE-2026-3731 https://www.cve.org/CVERecord?id=CVE-2026-3731 Référence CVE CVE-2026-3783 https://www.cve.org/CVERecord?id=CVE-2026-3783 Référence CVE CVE-2026-3784 https://www.cve.org/CVERecord?id=CVE-2026-3784 Gestion détaillée du document le 19 mars 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Conta

Official advisory
03

Patch and workaround

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.
Patch available
Affected
openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; rhaiis/vllm-cpu-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-25/lightspeed-chatbot-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2; rhoai/odh-llama-stack-core-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); satellite/foreman-mcp-server-rhel9 as a component of Red Hat Satellite 6; rhtas/segment-reporting-rhel9 as a component of Red Hat Trusted Artifact Signer
Fixed
automation-controller-venv-tower-0:4.6.28-3.el8ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; automation-controller-venv-tower-0:4.6.28-3.el8ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; automation-controller-venv-tower-0:4.6.28-3.el8ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; automation-controller-venv-tower-0:4.6.28-3.el8ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; python3.12-pyjwt+crypto-0:2.12.1-1.el8ap.noarch as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; python3.12-pyjwt-0:2.12.1-1.el8ap.noarch as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; python3.12-pyjwt-0:2.12.1-1.el8ap.src as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8; automation-controller-venv-tower-0:4.6.28-3.el9ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; automation-controller-venv-tower-0:4.6.28-3.el9ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; automation-controller-venv-tower-0:4.6.28-3.el9ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; automation-controller-venv-tower-0:4.6.28-3.el9ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; python3.12-pyjwt+crypto-0:2.12.1-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; python3.12-pyjwt-0:2.12.1-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; python3.12-pyjwt-0:2.12.1-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 9; automation-controller-0:4.7.11-2.el9ap.src as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-cli-0:4.7.11-2.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-0:4.7.11-2.el9ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-0:4.7.11-2.el9ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-0:4.7.11-2.el9ap.s390x as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-0:4.7.11-2.el9ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-server-0:4.7.11-2.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-ui-0:4.7.11-2.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-venv-tower-0:4.7.11-2.el9ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-venv-tower-0:4.7.11-2.el9ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-venv-tower-0:4.7.11-2.el9ap.s390x as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; automation-controller-venv-tower-0:4.7.11-2.el9ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; python3.12-pyjwt+crypto-0:2.12.1-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; python3.12-pyjwt-0:2.12.1-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; python3.12-pyjwt-0:2.12.1-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.6 for RHEL 9; fence-agents-0:4.16.0-5.el10_0.9.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); and 1166 more
Action
For details on how to apply this update, refer to Ansible Automation Platform documentation.
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 12 Mar 2026 · Last source change 10 Sept 2026, 12:05 UTC · CWE-345 · Insufficient Verification of Data Authenticity

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-08-14
European sourceENISA EUVD · EUVD-2026-11728
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
ENISA EUVD · EUVD-2026-11728↗Vendor CSAF · Red Hat Product Security↗CISA Vulnrichment SSVC evidence↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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.
Free version - for non-commercial use only.CVE-2026-32597 · cve.blacktree.nl