RHSA-2026:60866HighCVSS 9.1

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Published
August 29, 2026
Last Modified
September 5, 2026

🔗 CVE IDs covered (6)

CVE-2026-75975 →CVE-2026-76172 →CVE-2026-82562 →CVE-2026-73501 →CVE-2026-75899 →CVE-2026-75931 →

📋 Description

CVE-2026-73501 — github.com/getkin/kin-openapi: kin-openapi: kin-openapi: ValidationHandler.Load() Fail-Open Authentication Bypass via NoopAuthenticationFunc Default CVE-2026-75899 — fast-uri: fast-uri: Server-Side Request Forgery via repeated hostname percent-decoding CVE-2026-75931 — fast-uri: fast-uri: Host confusion via skipped IDN canonicalization CVE-2026-75975 — fast-uri: fast-uri: Server-side request forgery via malformed IPv6 normalization CVE-2026-76172 — fast-uri: fast-uri: URI parsing flaw enables server-side request forgery and redirects CVE-2026-82562 — qs: qs: Denial of Service via array limit bypass in query string parsing

🎯 Affected products4

  • Red Hat Hardened Images
  • grafana12-4-main@aarch64 as a component of Red Hat Hardened Images
  • grafana12-4-main@src as a component of Red Hat Hardened Images
  • grafana12-4-main@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ 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: Until an updated qs dependency is available in your Red Hat product, limit exposure as follows: 1. If your application calls qs.parse() directly, avoid enabling both comma:true and throwOnLimitExceeded:true when parsing untrusted query strings or urlencoded request bodies. Disable one of these non-default options, or upgrade qs to version 6.16.0 or later. 2. Where qs is included only as a transitive dependency, apply product updates that ship qs 6.16.0 or later when they become available. 3. Enforce HTTP request-line and request-body size limits at your ingress or application server. Because allocated memory scales with attacker-supplied input size, transport-layer limits bound worst-case impact. Host operating systems are not directly affected. These steps apply to application processes that use qs with the vulnerable configuration.

🔗 References (10)