{"schema":"vulnpedia.research/1","cve":"CVE-2026-115731","references":[{"url":"https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution","tags":["vendor-reference"],"source":"mitre","sourceId":"Perforce","modified":"2026-11-03T20:52:37.394Z","origins":[{"source":"mitre","sourceId":"Perforce","modified":"2026-11-03T20:52:37.394Z","url":"https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution"},{"source":"nvd","sourceId":"CVE-2026-115731","modified":"2026-11-17T19:17:45.707","url":"https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution"},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution"}]},{"url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731","tags":["government-resource"],"source":"mitre","sourceId":"CISA-ADP","modified":"2026-11-17T18:44:53.769Z","origins":[{"source":"mitre","sourceId":"CISA-ADP","modified":"2026-11-17T18:44:53.769Z","tags":["government-resource"],"url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731"},{"source":"nvd","sourceId":"CVE-2026-115731","modified":"2026-11-17T19:17:45.707","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:95652","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-remediation"],"url":"https://access.redhat.com/errata/RHSA-2026:95652"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:95653","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-remediation"],"url":"https://access.redhat.com/errata/RHSA-2026:95653"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:95655","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-remediation"],"url":"https://access.redhat.com/errata/RHSA-2026:95655"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:95656","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-remediation"],"url":"https://access.redhat.com/errata/RHSA-2026:95656"}]},{"url":"https://access.redhat.com/security/cve/CVE-2026-115731","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://access.redhat.com/security/cve/CVE-2026-115731"}]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2566451","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2566451"}]},{"url":"https://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wq","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wq"}]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115731","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115731"}]},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","tags":["vendor-advisory"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-advisory"],"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"url":"https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/"}]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-115731","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://www.cve.org/CVERecord?id=CVE-2026-115731"}]},{"url":"https://www.openwall.com/lists/oss-security/2026/11/03/14","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","tags":["vendor-reference"],"url":"https://www.openwall.com/lists/oss-security/2026/11/03/14"}]},{"source":"euvd","sourceId":"EUVD-2026-116495","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-116495","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-116495","tags":["ADVISORY"],"url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-116495"}]},{"url":"https://vulncheck.com/kev","tags":["ADVISORY"],"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","tags":["ADVISORY"],"url":"https://vulncheck.com/kev"}]},{"url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","tags":["KEV report"],"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","tags":["KEV report"],"url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json"}]},{"url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/comment/19s50topnnx5w/","tags":["KEV report"],"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","tags":["KEV report"],"url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/comment/19s50topnnx5w/"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"10Base-openvox-agent-6:openvox-agent-0:8.32.0-1.el10sat.aarch64","product":"openvox-agent-0:8.32.0-1.el10sat.aarch64 as a component of Satellite Client 6 for RHEL 10","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:95653"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el10sat?arch=aarch64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"7Server-satellite-client-openvox:openvox-agent-0:8.32.0-1.el7sat.src","product":"openvox-agent-0:8.32.0-1.el7sat.src as a component of Satellite Client 6 for RHEL 7","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:95653"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el7sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-openvox-agent-6:openvox-agent-0:8.32.0-1.el8sat.src","product":"openvox-agent-0:8.32.0-1.el8sat.src as a component of Satellite Client 6 for RHEL 8","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:95653"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el8sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16-capsule:python-pyyaml-0:6.0.1-1.el8pc.src","product":"python-pyyaml-0:6.0.1-1.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index\n\nRelease Notes:\n\nProvisioning 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.\n\nThis 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.","url":"https://access.redhat.com/errata/RHSA-2026:95655"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/python-pyyaml@6.0.1-1.el8pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16:openvox-server-0:8.18.0-1.el8sat.src","product":"openvox-server-0:8.18.0-1.el8sat.src as a component of Red Hat Satellite 6.16 for RHEL 8","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index\n\nRelease Notes:\n\nProvisioning 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.\n\nThis 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.","url":"https://access.redhat.com/errata/RHSA-2026:95655"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el8sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-openvox-agent-6:openvox-agent-0:8.32.0-1.el9sat.aarch64","product":"openvox-agent-0:8.32.0-1.el9sat.aarch64 as a component of Satellite Client 6 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:95653"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=aarch64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16-capsule:openvox-server-0:8.18.0-1.el9sat.noarch","product":"openvox-server-0:8.18.0-1.el9sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index\n\nRelease Notes:\n\nProvisioning 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.\n\nThis 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.","url":"https://access.redhat.com/errata/RHSA-2026:95655"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16-capsule:python3.11-pyyaml-0:6.0.1-1.el9pc.x86_64","product":"python3.11-pyyaml-0:6.0.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index\n\nRelease Notes:\n\nProvisioning 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.\n\nThis 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.","url":"https://access.redhat.com/errata/RHSA-2026:95655"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/python3.11-pyyaml@6.0.1-1.el9pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16:python-pyyaml-0:6.0.1-1.el9pc.src","product":"python-pyyaml-0:6.0.1-1.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index\n\nRelease Notes:\n\nProvisioning 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.\n\nThis 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.","url":"https://access.redhat.com/errata/RHSA-2026:95655"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/python-pyyaml@6.0.1-1.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.17-capsule:openvox-agent-0:8.32.0-1.el9sat.x86_64","product":"openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:95656"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.17:openvox-agent-0:8.32.0-1.el9sat.x86_64","product":"openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:95656"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.19-capsule:openvox-server-0:8.18.0-1.el9sat.noarch","product":"openvox-server-0:8.18.0-1.el9sat.noarch as a component of Red Hat Satellite 6.19 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index","url":"https://access.redhat.com/errata/RHSA-2026:95652"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.19:openvox-server-0:8.18.0-1.el9sat.src","product":"openvox-server-0:8.18.0-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9","status":"fixed","remediations":[{"category":"vendor_fix","details":"Before applying this update, make sure all previously released errata\nrelevant to your system have been applied.\n\nFor detailed instructions how to apply this update, refer to:\n\nhttps://docs.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index","url":"https://access.redhat.com/errata/RHSA-2026:95652"},{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"red_hat_satellite_6:puppet-agent","product":"puppet-agent as a component of Red Hat Satellite 6","status":"known_affected","remediations":[{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppet-agent","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"red_hat_satellite_6:puppet-agent.src","product":"puppet-agent.src as a component of Red Hat Satellite 6","status":"known_affected","remediations":[{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppet-agent?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"red_hat_satellite_6:puppetserver","product":"puppetserver as a component of Red Hat Satellite 6","status":"known_affected","remediations":[{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppetserver","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"red_hat_satellite_6:puppetserver.src","product":"puppetserver.src as a component of Red Hat Satellite 6","status":"known_affected","remediations":[{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppetserver?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"red_hat_satellite_client:openvox-agent.src","product":"openvox-agent.src as a component of Red Hat Satellite Client","status":"known_affected","remediations":[{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/openvox-agent?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"red_hat_satellite_client:puppet-agent.src","product":"puppet-agent.src as a component of Red Hat Satellite Client","status":"known_affected","remediations":[{"category":"workaround","details":"Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate.\n\n--- CME Mitigation Guidance (2026-11-04) ---\nDisclaimer: 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.\n\nThe 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.\n\nHighest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppet-agent?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16-capsule:openvox-agent-0:8.32.0-1.el8sat.src","product":"openvox-agent-0:8.32.0-1.el8sat.src as a component of Red Hat Satellite 6.16 for RHEL 8","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el8sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16-capsule:python-pulp-ansible-1:0.21.19-2.el8pc.src","product":"python-pulp-ansible-1:0.21.19-2.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python-pulp-ansible@0.21.19-2.el8pc?arch=src&epoch=1","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16-capsule:python3.11-pulp-ansible-1:0.21.19-2.el8pc.noarch","product":"python3.11-pulp-ansible-1:0.21.19-2.el8pc.noarch as a component of Red Hat Satellite 6.16 for RHEL 8","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python3.11-pulp-ansible@0.21.19-2.el8pc?arch=noarch&epoch=1","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16:python-pillow-debugsource-0:13.0.0-1.el8pc.x86_64","product":"python-pillow-debugsource-0:13.0.0-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python-pillow-debugsource@13.0.0-1.el8pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"8Base-satellite-6.16:python3.11-pillow-debuginfo-0:13.0.0-1.el8pc.x86_64","product":"python3.11-pillow-debuginfo-0:13.0.0-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python3.11-pillow-debuginfo@13.0.0-1.el8pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16-capsule:python-nh3-0:0.3.0-2.el9pc.src","product":"python-nh3-0:0.3.0-2.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python-nh3@0.3.0-2.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16-capsule:python3.11-pillow-0:13.0.0-1.el9pc.x86_64","product":"python3.11-pillow-0:13.0.0-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python3.11-pillow@13.0.0-1.el9pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16:python-gitpython-0:3.2.1-1.el9pc.src","product":"python-gitpython-0:3.2.1-1.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python-gitpython@3.2.1-1.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.16:python3.11-gitpython-0:3.2.1-1.el9pc.noarch","product":"python3.11-gitpython-0:3.2.1-1.el9pc.noarch as a component of Red Hat Satellite 6.16 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python3.11-gitpython@3.2.1-1.el9pc?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.17-capsule:python-pillow-0:13.0.0-1.el9pc.src","product":"python-pillow-0:13.0.0-1.el9pc.src as a component of Red Hat Satellite 6.17 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python-pillow@13.0.0-1.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.17-capsule:python3.11-pulp-ansible-1:0.22.11-1.el9pc.noarch","product":"python3.11-pulp-ansible-1:0.22.11-1.el9pc.noarch as a component of Red Hat Satellite 6.17 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python3.11-pulp-ansible@0.22.11-1.el9pc?arch=noarch&epoch=1","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.17:python3.11-brotli-debuginfo-0:1.2.1-1.el9pc.x86_64","product":"python3.11-brotli-debuginfo-0:1.2.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/python3.11-brotli-debuginfo@1.2.1-1.el9pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]},{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json","productId":"9Base-satellite-6.19:openvox-agent-0:8.32.0-1.el9sat.x86_64","product":"openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.19 for RHEL 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115731","modified":"2026-11-10T08:29:16+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115731.json"}]}],"vendorCoverage":{"total":169,"shown":32,"omitted":137,"source":"redhat"},"exploitationSources":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","catalog":"VulnCheck KEV","kind":"catalogue","url":"https://vulncheck.com/kev","dateAdded":"2026-11-04T00:00:00Z","modified":"2026-11-04T00:00:00Z","requiredAction":"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.","knownRansomwareCampaignUse":"Unknown","reportedByVulncheckCanaries":false,"vendorProject":"Perforce","product":"Puppet Enterprise","dueDate":"2026-12-01T00:00:00Z","cisaDateAdded":"2026-11-17T00:00:00Z","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","modified":"2026-11-04T00:00:00Z","url":"https://vulncheck.com/kev"}]},{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","catalog":"VulnCheck KEV","kind":"report","url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/comment/19s50topnnx5w/","dateAdded":"2026-11-04T00:00:00Z","firstPartyCanary":false,"origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/comment/19s50topnnx5w/"}]},{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","catalog":"VulnCheck KEV","kind":"report","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json","dateAdded":"2026-11-17T00:00:00Z","firstPartyCanary":false,"origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115731","url":"https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json"}]}],"sourceTimes":{"cisa-kev":"2026-11-17T20:16:50.787Z","exploitdb":"2026-11-17T20:16:50.787Z","epss":"2026-11-17T16:17:06.452Z","nuclei":"2026-11-17T16:17:06.452Z","osv-PyPI":"2026-11-17T04:27:59.087Z","osv-npm":"2026-11-17T04:28:15.939Z","osv-Maven":"2026-11-17T04:28:01.586Z","osv-Go":"2026-11-17T04:28:02.946Z","osv-crates_io":"2026-11-17T04:28:03.528Z","osv-RubyGems":"2026-11-17T04:28:04.373Z","osv-Packagist":"2026-11-17T04:28:06.135Z","osv-NuGet":"2026-11-17T04:28:07.122Z","osv-Pub":"2026-11-17T04:28:07.350Z","osv-SwiftURL":"2026-11-17T04:28:07.501Z","osv-GitHub_Actions":"2026-11-17T04:28:07.633Z","osv-_EMPTY_":"2026-11-17T04:28:10.211Z","poc-in-github":"2026-11-17T04:28:13.897Z","metasploit":"2026-11-17T20:16:50.787Z","redhat-vex":"2026-11-17T04:33:40.770Z","euvd":"2026-11-17T04:27:48.925Z","vulncheck-kev":"2026-11-17T20:16:50.787Z","zdi":"2026-11-17T20:16:50.787Z","oss-security":"2026-11-17T20:16:50.787Z","full-disclosure":"2026-11-17T20:16:50.787Z","cert-cc":"2026-11-17T20:16:50.787Z","watchtowr":"2026-11-17T20:16:50.787Z","lexfo":"2026-11-17T20:16:50.787Z","google-security-research":"2026-11-17T20:16:50.787Z","vulncheck-initial-access":"2026-11-17T20:16:50.787Z","fkie-nvd-2026":"2026-11-17T16:17:10.644Z","fkie-nvd-2025":"2026-11-17T04:27:44.402Z","ghsa":"2026-11-17T20:17:23.984Z","pysec":"2026-11-17T20:17:23.984Z","go":"2026-11-17T20:17:23.984Z","rustsec":"2026-11-17T20:17:23.984Z","primary":"2026-11-17T18:44:53.769Z","nvd":"2026-11-17T19:17:45.707"},"sourceFields":{"schema":"vulnpedia.source-fields/1","primary":{"description":"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.","published":"2026-11-03","cwe":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-94","name":"Improper Control of Generation of Code ('Code Injection')"}],"labels":{"vendors":["Perforce"],"products":["Puppet Enterprise"]},"ssvc":{"exploitation":"active","automatable":"no","technicalImpact":"total"}},"nvd":{"description":"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.","published":"2026-11-03","cwe":[{"id":"CWE-94","name":"Code injection"},{"id":"CWE-502","name":"Deserialization of untrusted data"}],"labels":{"vendors":[],"products":[]},"ssvc":{"exploitation":"active","automatable":"no","technicalImpact":"total"}}},"labels":{"vendors":["Perforce"],"products":["Puppet Enterprise"]},"freshness":{"checkedAt":"2026-11-17T20:29:31.791Z","changedAt":"2026-11-17T19:48:54.230Z","pocChangedAt":null,"addedPoCs":[],"removedPoCs":[],"changedPoCs":[]},"evidence":{"version":"2026-11-17T20:29:31.791Z#a1168c9286d25ca77199aae10764400daa654cd7d7a5cab0bff4e7abf6852e7f","checkedAt":"2026-11-17T20:29:31.791Z","changedAt":"2026-11-17T19:48:54.230Z","pocChangedAt":null}}