← Search CVEs

CVE-2026-115732

CRITICAL 9 UPDATED SOURCE DATA

Published 2026-11-03 · Last modified 2026-11-06 · Perforce · NVD: Awaiting Analysis

Evidence updated · Checked

Source catalogue and publisher evidence; linked resources have not been executed or independently validated by Vulnpedia.

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.

REPORTED EXPLOITATION

VulnCheck KEV reports exploitation for this CVE. These are source-specific reports; review the details and vendor guidance below.

Exploitation likelihood

0.7%chance of exploitation in 30 days · 55th percentile

○ In CISA KEV○ Catalogued PoC◆ SSVC: exploitation none, automatable no

Impact if exploited

9CVSS 4.0 · CRITICAL · CNA

  • ConfidentialityHigh
  • IntegrityHigh
  • AvailabilityHigh

What an attacker needs

  • ✓Access: Reachable over the network — no local access needed
  • ⚠Privileges: Requires a low-privilege account
  • ✓User interaction: No user interaction needed
  • ✓Complexity: No special conditions — reliably repeatable
  • ⚠Requirements: Specific conditions must be present

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

No public PoC is currently catalogued.

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Supported CVE and PoC feeds are scheduled every 30 minutes, including for older CVEs. Other enrichment runs daily or weekly; source availability can delay updates. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Perforce

Products Puppet Enterprise

Weakness (CWE)

  • CWE-863: Incorrect Authorization
  • CWE-697: Incorrect Comparison

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

References and research data (JSON) · Change history

Vendor product assessments

Showing 32 of 154 vendor product statements; 122 omitted. Read the full vendor advisory.

  • openvox-server-0:8.18.0-1.el8sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 8 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el8sat?arch=noarch

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-pyyaml-0:6.0.1-1.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/python-pyyaml@6.0.1-1.el8pc?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el8sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 8 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el8sat?arch=noarch

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-pyyaml-0:6.0.1-1.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/python-pyyaml@6.0.1-1.el8pc?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el9sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-pyyaml-0:6.0.1-1.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/python-pyyaml@6.0.1-1.el9pc?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el9sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=noarch

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-pyyaml-0:6.0.1-1.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/python-pyyaml@6.0.1-1.el9pc?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-pyyaml-0:6.0.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/python3.11-pyyaml@6.0.1-1.el9pc?arch=x86_64

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with the Red Hat family set. Attempts to download an unattended template without a valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk, which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data. Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-server-0:8.18.0-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9 · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/openvox-server@8.18.0-1.el9sat?arch=src

    • vendor fix: Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index Vendor guidance
    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • puppetserver as a component of Red Hat Satellite 6 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/puppetserver

    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    • none available: Affected
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • puppetserver.src as a component of Red Hat Satellite 6 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/puppetserver?arch=src

    • workaround: Until patched, avoid autosigning certificate requests without strong verification, and do not approve CSRs for names that are suffixes/prefixes of existing authorized certnames. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce 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. Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
    • none available: Affected
    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-agent-0:8.32.0-1.el8sat.src as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/openvox-agent@8.32.0-1.el8sat?arch=src

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-pillow-debugsource-0:13.0.0-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-pillow-debugsource@13.0.0-1.el8pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-pillow-0:13.0.0-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python3.11-pillow@13.0.0-1.el8pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-django-0:4.2.30-2.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-django@4.2.30-2.el8pc?arch=src

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-brotli-debuginfo-0:1.2.1-1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python3.11-brotli-debuginfo@1.2.1-1.el8pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-agent-0:8.32.0-1.el9sat.src as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=src

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-pillow-debugsource-0:13.0.0-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-pillow-debugsource@13.0.0-1.el9pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-pillow-0:13.0.0-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python3.11-pillow@13.0.0-1.el9pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-django-0:4.2.30-2.el9pc.src as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-django@4.2.30-2.el9pc?arch=src

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-brotli-debuginfo-0:1.2.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python3.11-brotli-debuginfo@1.2.1-1.el9pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-brotli-0:1.2.1-1.el9pc.src as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-brotli@1.2.1-1.el9pc?arch=src

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-brotli-debuginfo-0:1.2.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python3.11-brotli-debuginfo@1.2.1-1.el9pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python-brotli-debugsource-0:1.2.1-1.el9pc.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-brotli-debugsource@1.2.1-1.el9pc?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • python3.11-django-0:4.2.30-2.el9pc.noarch as a component of Red Hat Satellite 6.17 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python3.11-django@4.2.30-2.el9pc?arch=noarch

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00
  • openvox-agent-0:8.32.0-1.el9sat.x86_64 as a component of Red Hat Satellite 6.19 for RHEL 9 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/openvox-agent@8.32.0-1.el9sat?arch=x86_64

    Red Hat · CVE-2026-115732 · Updated 2026-11-06T00:30:14+00:00

Additional exploitation reports

Source-specific reports, separate from CISA KEV. Repeated observations from one source are not independent confirmations.

  • VulnCheck KEV · 2026-11-04T00:00:00Z

    Source guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

    Source ransomware assessment: Unknown

    VulnCheck KEV · CVE-2026-115732 · Updated 2026-11-04T00:00:00Z
  • VulnCheck KEV · 2026-11-04T00:00:00ZVulnCheck KEV · CVE-2026-115732

All CVSS metrics

  • CRITICAL 9 v4.0 · CNA Primary
    CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
  • CRITICAL 9 v4.0 · NVD Secondary
    CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

Advisories

Technical & other

Sources: NVD · CVE.org · All sources and attribution · EPSS