CVE-2026-115731
CRITICAL 9.4 KNOWN EXPLOITED UPDATED SOURCE DATASource catalogue and publisher evidence; linked resources have not been executed or independently validated by Vulnpedia.
Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type via PUT request. Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate.
Confirmed exploited in the wild — in CISA KEV since 2026-11-17. Patch or mitigate now.
Exploitation likelihood
0.4%chance of exploitation in 30 days · 31st percentile
Impact if exploited
9.4CVSS 4.0 · CRITICAL · CNA
- ConfidentialityHigh
- IntegrityHigh
- AvailabilityHigh
What an attacker needs
- ✓Access: Reachable over the network — no local access needed
- ⚠Privileges: Requires a low-privilege account
- ✓User interaction: No user interaction needed
- ✓Complexity: No special conditions — reliably repeatable
- ✓Requirements: No special attack requirements
✓ lowers the bar for an attacker · ⚠ raises it
Proof of concept
No public PoC is currently catalogued.
Search for new PoCs
Search GitHub now — results may be empty or unverified.
Supported CVE and PoC feeds are scheduled every 30 minutes, including for older CVEs. Other enrichment runs daily or weekly; source availability can delay updates. A later release appears after a tracked source lists it and a refresh succeeds.
Data snapshot:
Weakness (CWE)
- CWE-502: Deserialization of Untrusted Data
- CWE-94: Improper Control of Generation of Code ('Code Injection')
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
References and research data (JSON) · Change history
Vendor product assessments
Showing 32 of 169 vendor product statements; 137 omitted. Read the full vendor advisory.
openvox-agent-0:8.32.0-1.el10sat.aarch64 as a component of Satellite Client 6 for RHEL 10 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent@8.32.0-1.el10sat?arch=aarch64
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-agent-0:8.32.0-1.el7sat.src as a component of Satellite Client 6 for RHEL 7 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent@8.32.0-1.el7sat?arch=src
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-agent-0:8.32.0-1.el8sat.src as a component of Satellite Client 6 for RHEL 8 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent@8.32.0-1.el8sat?arch=src
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
python-pyyaml-0:6.0.1-1.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/python-pyyaml@6.0.1-1.el8pc?arch=src
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-server-0:8.18.0-1.el8sat.src as a component of Red Hat Satellite 6.16 for RHEL 8 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-server@8.18.0-1.el8sat?arch=src
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-agent-0:8.32.0-1.el9sat.aarch64 as a component of Satellite Client 6 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=aarch64
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-server-0:8.18.0-1.el9sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
python3.11-pyyaml-0:6.0.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/python3.11-pyyaml@6.0.1-1.el9pc?arch=x86_64
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
python-pyyaml-0:6.0.1-1.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/python-pyyaml@6.0.1-1.el9pc?arch=src
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-server-0:8.18.0-1.el9sat.noarch as a component of Red Hat Satellite 6.19 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
openvox-server-0:8.18.0-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9 · fixed
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src
- vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index Vendor guidance
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
puppet-agent as a component of Red Hat Satellite 6 · known affected
Vendor assessment for this product only.
pkg:rpm/redhat/puppet-agent
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
- none available: Affected
puppet-agent.src as a component of Red Hat Satellite 6 · known affected
Vendor assessment for this product only.
pkg:rpm/redhat/puppet-agent?arch=src
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
- none available: Affected
puppetserver as a component of Red Hat Satellite 6 · known affected
Vendor assessment for this product only.
pkg:rpm/redhat/puppetserver
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
- none available: Affected
puppetserver.src as a component of Red Hat Satellite 6 · known affected
Vendor assessment for this product only.
pkg:rpm/redhat/puppetserver?arch=src
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
- none available: Affected
openvox-agent.src as a component of Red Hat Satellite Client · known affected
Vendor assessment for this product only.
pkg:rpm/redhat/openvox-agent?arch=src
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
- none available: Affected
puppet-agent.src as a component of Red Hat Satellite Client · known affected
Vendor assessment for this product only.
pkg:rpm/redhat/puppet-agent?arch=src
- workaround: Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to openvox-server 9.2.0 and 8.18.0, Puppet Core agent 9.1.3 and 8.22.2 (or the fixed Openvox Server/Puppetserver builds), which restricts deserialization of report events to safe expected types to block untrusted __ptype instantiation and dynamic evaluation, closing crafted JSON report containing malicious serialized rich-data event types submitted via HTTP PUT. Until patched, this is a concern on Puppet Server and OpenVox Server instances processing agent reports, so avoid autosigning certificate requests without strong verification and restrict network access to the PUT /puppet/v3/report endpoint. As a compensating measure, enforce strict allowlist validation over report payload schemas and event structures before deserialization, deploy EDR to detect anomalous child processes and post-exploitation activity spawned by the puppetserver service user, configure auditd to log unauthorized system calls and command executions initiated by the puppetserver daemon, and use Falco or eBPF runtime security to detect unexpected shell invocations or sensitive credential reads by puppetserver. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted deserialization defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)
- none available: Affected
openvox-agent-0:8.32.0-1.el8sat.src as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/openvox-agent@8.32.0-1.el8sat?arch=src
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python-pulp-ansible-1:0.21.19-2.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python-pulp-ansible@0.21.19-2.el8pc?arch=src&epoch=1
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python3.11-pulp-ansible-1:0.21.19-2.el8pc.noarch as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python3.11-pulp-ansible@0.21.19-2.el8pc?arch=noarch&epoch=1
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python-pillow-debugsource-0:13.0.0-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python-pillow-debugsource@13.0.0-1.el8pc?arch=x86_64
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python3.11-pillow-debuginfo-0:13.0.0-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python3.11-pillow-debuginfo@13.0.0-1.el8pc?arch=x86_64
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python-nh3-0:0.3.0-2.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python-nh3@0.3.0-2.el9pc?arch=src
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python3.11-pillow-0:13.0.0-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python3.11-pillow@13.0.0-1.el9pc?arch=x86_64
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python-gitpython-0:3.2.1-1.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python-gitpython@3.2.1-1.el9pc?arch=src
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python3.11-gitpython-0:3.2.1-1.el9pc.noarch as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python3.11-gitpython@3.2.1-1.el9pc?arch=noarch
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python-pillow-0:13.0.0-1.el9pc.src as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python-pillow@13.0.0-1.el9pc?arch=src
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python3.11-pulp-ansible-1:0.22.11-1.el9pc.noarch as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python3.11-pulp-ansible@0.22.11-1.el9pc?arch=noarch&epoch=1
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00python3.11-brotli-debuginfo-0:1.2.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/python3.11-brotli-debuginfo@1.2.1-1.el9pc?arch=x86_64
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.19 for RHEL 9 · known not affected
Vendor assessment for this product only.
Reason: vulnerable code not present
pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
Additional exploitation reports
Source-specific reports, separate from CISA KEV. Repeated observations from one source are not independent confirmations.
- VulnCheck KEV · 2026-11-04T00:00:00Z
Source guidance: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Source ransomware assessment: Unknown
VulnCheck KEV · CVE-2026-115731 · Updated 2026-11-04T00:00:00Z - VulnCheck KEV · 2026-11-04T00:00:00ZVulnCheck KEV · CVE-2026-115731
- VulnCheck KEV · 2026-11-17T00:00:00ZVulnCheck KEV · CVE-2026-115731
All CVSS metrics
- CRITICAL 9.4 v4.0 · CNA Primary
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H - CRITICAL 9.4 v4.0 · NVD Secondary
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Advisories
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731 CVE record · CISA-ADP · Updated 2026-11-17T18:44:53.769Z
NVD · CVE-2026-115731 · Updated 2026-11-17T19:17:45.707 - https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-116495 EUVD · EUVD-2026-116495
- https://vulncheck.com/kev VulnCheck KEV · CVE-2026-115731 · Updated 2026-11-04T00:00:00Z
Technical & other
- https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution CVE record · Perforce · Updated 2026-11-03T20:52:37.394Z
NVD · CVE-2026-115731 · Updated 2026-11-17T19:17:45.707
Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00 - https://access.redhat.com/errata/RHSA-2026:95652 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://access.redhat.com/errata/RHSA-2026:95653 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://access.redhat.com/errata/RHSA-2026:95655 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://access.redhat.com/errata/RHSA-2026:95656 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://access.redhat.com/security/cve/CVE-2026-115731 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://bugzilla.redhat.com/show_bug.cgi?id=2566451 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wq Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://nvd.nist.gov/vuln/detail/CVE-2026-115731 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/ Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://www.cve.org/CVERecord?id=CVE-2026-115731 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://www.openwall.com/lists/oss-security/2026/11/03/14 Red Hat · CVE-2026-115731 · Updated 2026-11-10T08:29:16+00:00
- https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json VulnCheck KEV · CVE-2026-115731 · Updated 2026-11-04T00:00:00Z
- https://www.reddit.com/r/Puppet/comments/1xnj0v1/comment/19s50topnnx5w/ VulnCheck KEV · CVE-2026-115731 · Updated 2026-11-04T00:00:00Z
Sources: NVD · CVE.org · All sources and attribution · EPSS