RHSA-2026:42150HighCVSS 9.1

Red Hat Security Advisory: Satellite 6.17.9.1 Async Update

Published
July 20, 2026
Last Modified
July 27, 2026

🔗 CVE IDs covered (6)

CVE-2026-12701 →CVE-2026-25679 →CVE-2026-27145 →CVE-2026-33186 →CVE-2026-33811 →CVE-2026-39821 →

📋 Description

CVE-2026-12701 — pulpcore: pulpcore: relative_path_validator bypass via directory traversal in FilesystemExport CVE-2026-25679 — net/url: Incorrect parsing of IPv6 host literals in net/url CVE-2026-27145 — crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries CVE-2026-33186 — google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME CVE-2026-39821 — golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing

🎯 Affected products13

  • Red Hat Satellite 6.17 for RHEL 9
  • python-pulp-rpm-0:3.27.12-1.el9pc.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • python-pulpcore-0:3.63.21-2.el9pc.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • python3.11-pulp-rpm-0:3.27.12-1.el9pc.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • python3.11-pulpcore-0:3.63.21-2.el9pc.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • satellite-0:6.17.9.1-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • satellite-0:6.17.9.1-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • satellite-capsule-0:6.17.9.1-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • satellite-cli-0:6.17.9.1-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • satellite-common-0:6.17.9.1-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • satellite-obsolete-packages-0:6.17.9.1-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • yggdrasil-worker-forwarder-0:0.0.4-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • yggdrasil-worker-forwarder-0:0.0.4-1.el9sat.x86_64 as a component of Red Hat Satellite 6.17 for RHEL 9

✅ Remediation

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.17/html/updating_red_hat_satellite/index Workaround: There is no complete mitigation for this vulnerability. The following measures can reduce risk: 1. If FilesystemExport was never configured on your deployment, you are not affected by this issue. 2. If FilesystemExporters exist in the database, audit them for path traversal sequences ("../"). Existing malicious entries must be cleaned up manually, as the validation functions documented to raise ValidationError do not actually do so in all code paths. 3. Restrict admin-level access to the Pulp API to only trusted operators. Review and audit which accounts have administrator privileges. 4. Ensure SELinux is in enforcing mode on Satellite/Pulp servers to limit the directories the Pulp service user can write to. 5. Monitor filesystem changes outside of expected Pulp directories for signs of exploitation. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: A flaw was found in the Go standard library crypto/x509 package. When verifying a TLS certificate hostname, VerifyHostname processed each DNS Subject Alternative Name (SAN) entry in a loop and repeatedly split the candidate hostname on "." characters. For certificates with a very large DNS SAN list, CPU use could grow quadratically with the number of SAN entries and hostname labels. Because hostname verification runs before the certificate chain is built, this overhead can occur even when the certificate is not trusted. Red Hat rates this issue as Important. It affects Red Hat products that include the Go standard library crypto/x509 code from an affected Go toolchain version (before Go 1.25.11, or from Go 1.26.0 through Go 1.26.3). Applications and container images built with a fixed Go release (1.25.11 or later, or 1.26.4 or later) are not affected. Community distributions such as Fedora are also affected. Upstream fix: Go 1.25.11 and Go 1.26.4 (GO-2026-5037). Workaround: To mitigate this issue, implement infrastructure-level normalization to ensure all incoming HTTP/2 `:path` headers are properly formatted with a leading slash before reaching the gRPC-Go server. This can be achieved by configuring a reverse proxy or API gateway to validate and normalize the `:path` header. Ensure that any such intermediary is properly configured and restarted to apply the changes, which may temporarily impact service availability. Workaround: To mitigate this issue, applications can be configured to use the pure Go DNS resolver instead of the `cgo` DNS resolver. This can be achieved by setting the `GODEBUG` environment variable to `netdns=go`. For example, to run a Go application with this mitigation: `GODEBUG=netdns=go /path/to/your/go/application`. This change may require restarting affected applications or services to take effect. Users should verify that this change does not negatively impact DNS resolution for their specific application environment. Workaround: Upgrade to a fixed golang.org/x/net release that includes the idna correction, via updated golang or dependent package rebuilds.

🔗 References (10)