{"schema":"vulnpedia.research/1","cve":"CVE-2026-115732","references":[{"url":"https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass","tags":["vendor-reference"],"source":"mitre","sourceId":"Perforce","modified":"2026-11-03T20:38:24.169Z","origins":[{"source":"mitre","sourceId":"Perforce","modified":"2026-11-03T20:38:24.169Z","url":"https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass"},{"source":"nvd","sourceId":"CVE-2026-115732","modified":"2026-11-06T20:38:53.570","url":"https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass"},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:95652","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-remediation"],"url":"https://access.redhat.com/errata/RHSA-2026:95652"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:95655","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+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-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-remediation"],"url":"https://access.redhat.com/errata/RHSA-2026:95656"}]},{"url":"https://access.redhat.com/security/cve/CVE-2026-115732","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://access.redhat.com/security/cve/CVE-2026-115732"}]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2566291","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2566291"}]},{"url":"https://github.com/OpenVoxProject/trapperkeeper-authorization/security/advisories/GHSA-q4hm-33rc-572g","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://github.com/OpenVoxProject/trapperkeeper-authorization/security/advisories/GHSA-q4hm-33rc-572g"}]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115732","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115732"}]},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","tags":["vendor-advisory"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-advisory"],"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"url":"https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+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-115732","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://www.cve.org/CVERecord?id=CVE-2026-115732"}]},{"url":"https://www.openwall.com/lists/oss-security/2026/11/03/14","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","tags":["vendor-reference"],"url":"https://www.openwall.com/lists/oss-security/2026/11/03/14"}]},{"source":"euvd","sourceId":"EUVD-2026-116493","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-116493","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-116493","tags":["ADVISORY"],"url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-116493"}]},{"url":"https://vulncheck.com/kev","tags":["ADVISORY"],"source":"vulncheck-kev","sourceId":"CVE-2026-115732","modified":"2026-11-04T00:00:00Z","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115732","modified":"2026-11-04T00:00:00Z","tags":["ADVISORY"],"url":"https://vulncheck.com/kev"}]},{"url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/cve2026115732_published_114_being_exploited_in/","tags":["KEV report"],"source":"vulncheck-kev","sourceId":"CVE-2026-115732","modified":"2026-11-04T00:00:00Z","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115732","modified":"2026-11-04T00:00:00Z","tags":["KEV report"],"url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/cve2026115732_published_114_being_exploited_in/"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16-capsule:openvox-server-0:8.18.0-1.el8sat.noarch","product":"openvox-server-0:8.18.0-1.el8sat.noarch 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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el8sat?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/python-pyyaml@6.0.1-1.el8pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16:openvox-server-0:8.18.0-1.el8sat.noarch","product":"openvox-server-0:8.18.0-1.el8sat.noarch 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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el8sat?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16: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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/python-pyyaml@6.0.1-1.el8pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16-capsule: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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/python-pyyaml@6.0.1-1.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16: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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/python-pyyaml@6.0.1-1.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16: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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/python3.11-pyyaml@6.0.1-1.el9pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.17-capsule: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.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.17: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.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.19-capsule: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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"}],"purl":"pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppetserver","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames.\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 exact domain segment length matching and full domain equality for certificate hostname ACL checks in trapperkeeper-authorization: upgrade to openvox-server and openvoxdb 9.2.0, 8.18.0 (or the fixed Puppetserver/Openvox Server builds), which require domain segment counts to match for non-wildcard rules or validate full domain equality during ACL evaluation, closing all 2 injection vectors (subdomain certificate acquisition via autosigning, prefix or suffix certificate signing via CA approval). Until patched, this is a concern on Puppet Server, OpenVox Server, and OpenVoxDB deployments, so Avoid autosigning certificate requests without strict verification, reject CSR approvals for names that extend or shorten authorized certnames, and restrict network access to server endpoints. As a compensating measure, Deploy EDR agents to detect anomalous post-exploitation activity and unauthorized command execution on nodes targeted through catalog impersonation, Configure Falco or eBPF runtime security to detect anomalous process executions and unexpected shells spawned following catalog-driven execution, and Integrate application admin event logging with SIEM to detect unauthorized CA administrative operations or node catalog downloads with mismatched certnames. These controls limit blast radius and contain exploitation, but they do not fix the underlying flawed hostname ACL matching defect — apply the upstream patch to fully remediate.\n\nHighest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/puppetserver?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16-capsule: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-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16-capsule:python3.11-pillow-0:13.0.0-1.el8pc.x86_64","product":"python3.11-pillow-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@13.0.0-1.el8pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16:python-django-0:4.2.30-2.el8pc.src","product":"python-django-0:4.2.30-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-django@4.2.30-2.el8pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"8Base-satellite-6.16:python3.11-brotli-debuginfo-0:1.2.1-1.el8pc.x86_64","product":"python3.11-brotli-debuginfo-0:1.2.1-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-brotli-debuginfo@1.2.1-1.el8pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16-capsule:openvox-agent-0:8.32.0-1.el9sat.src","product":"openvox-agent-0:8.32.0-1.el9sat.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/openvox-agent@8.32.0-1.el9sat?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16-capsule:python-pillow-debugsource-0:13.0.0-1.el9pc.x86_64","product":"python-pillow-debugsource-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/python-pillow-debugsource@13.0.0-1.el9pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16:python-django-0:4.2.30-2.el9pc.src","product":"python-django-0:4.2.30-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-django@4.2.30-2.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.16: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.16 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-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.17-capsule:python-brotli-0:1.2.1-1.el9pc.src","product":"python-brotli-0:1.2.1-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-brotli@1.2.1-1.el9pc?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.17-capsule: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-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.17:python-brotli-debugsource-0:1.2.1-1.el9pc.x86_64","product":"python-brotli-debugsource-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/python-brotli-debugsource@1.2.1-1.el9pc?arch=x86_64","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json","productId":"9Base-satellite-6.17:python3.11-django-0:4.2.30-2.el9pc.noarch","product":"python3.11-django-0:4.2.30-2.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-django@4.2.30-2.el9pc?arch=noarch","origins":[{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]},{"source":"redhat","sourceId":"CVE-2026-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.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-115732","modified":"2026-11-06T00:30:14+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-115732.json"}]}],"vendorCoverage":{"total":154,"shown":32,"omitted":122,"source":"redhat"},"exploitationSources":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115732","catalog":"VulnCheck KEV","kind":"catalogue","url":"https://vulncheck.com/kev","dateAdded":"2026-11-04T00:00:00Z","modified":"2026-11-04T00:00:00Z","requiredAction":"Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.","knownRansomwareCampaignUse":"Unknown","reportedByVulncheckCanaries":false,"vendorProject":"Perforce","product":"Puppet Enterprise","origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115732","modified":"2026-11-04T00:00:00Z","url":"https://vulncheck.com/kev"}]},{"source":"vulncheck-kev","sourceId":"CVE-2026-115732","catalog":"VulnCheck KEV","kind":"report","url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/cve2026115732_published_114_being_exploited_in/","dateAdded":"2026-11-04T00:00:00Z","firstPartyCanary":false,"origins":[{"source":"vulncheck-kev","sourceId":"CVE-2026-115732","url":"https://www.reddit.com/r/Puppet/comments/1xnj0v1/cve2026115732_published_114_being_exploited_in/"}]}],"sourceTimes":{"cisa-kev":"2026-11-17T16:17:06.452Z","exploitdb":"2026-11-17T16:17:06.452Z","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-17T04:28:14.294Z","redhat-vex":"2026-11-17T04:33:40.770Z","euvd":"2026-11-17T04:27:48.925Z","vulncheck-kev":"2026-11-17T04:27:54.912Z","zdi":"2026-11-17T16:17:21.970Z","oss-security":"2026-11-17T16:17:21.970Z","full-disclosure":"2026-11-17T16:17:21.970Z","cert-cc":"2026-11-17T16:17:21.970Z","watchtowr":"2026-11-17T16:17:21.970Z","lexfo":"2026-11-17T16:17:21.970Z","google-security-research":"2026-11-17T16:17:21.970Z","vulncheck-initial-access":"2026-11-17T16:17:21.970Z","fkie-nvd-2026":"2026-11-17T16:17:10.644Z","fkie-nvd-2025":"2026-11-17T04:27:44.402Z","ghsa":"2026-11-17T04:27:59.087Z","pysec":"2026-11-17T04:27:59.087Z","go":"2026-11-17T04:27:59.087Z","rustsec":"2026-11-17T04:27:59.087Z","primary":"2026-11-06T19:39:07.902Z","nvd":"2026-11-06T20:38:53.570"},"sourceFields":{"schema":"vulnpedia.source-fields/1","primary":{"description":"Incorrect authorization in the certificate-name matching of trapperkeeper-authorization, as used by Puppet Server, in the affected products, allows a client that holds a CA-signed certificate whose name extends or shortens an authorized hostname to be authorized as that host. This enables impersonation of other nodes and, in Puppet Enterprise, access to certificate-authority administration and remote command execution on managed nodes. Exploitation requires a certificate with a colliding name, which the certificate authority issues by approval or autosign.","published":"2026-11-03","cwe":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-697","name":"Incorrect Comparison"}],"labels":{"vendors":["Perforce"],"products":["Puppet Enterprise"]},"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total"}},"nvd":{"description":"Incorrect authorization in the certificate-name matching of trapperkeeper-authorization, as used by Puppet Server, in the affected products, allows a client that holds a CA-signed certificate whose name extends or shortens an authorized hostname to be authorized as that host. This enables impersonation of other nodes and, in Puppet Enterprise, access to certificate-authority administration and remote command execution on managed nodes. Exploitation requires a certificate with a colliding name, which the certificate authority issues by approval or autosign.","published":"2026-11-03","cwe":[{"id":"CWE-697","name":"Incorrect Comparison"},{"id":"CWE-863","name":"Incorrect authorization"}],"labels":{"vendors":[],"products":[]},"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total"}}},"labels":{"vendors":["Perforce"],"products":["Puppet Enterprise"]},"evidence":{"version":"2026-11-17T16:17:37.769Z#e12ce7d58ebc66545d9a1afae82d869bd101d78caeeb5d148cff2f575bc85407","checkedAt":"2026-11-17T16:17:37.769Z","changedAt":"2026-11-16T23:39:03.167Z","pocChangedAt":null}}