RHSA-2026:6568HighCVSS 9.1

Red Hat Security Advisory: Red Hat Quay 3.15.4

Published
April 3, 2026
Last Modified
August 20, 2026

🔗 CVE IDs covered (26)

CVE-2026-25990 →CVE-2026-28802 →CVE-2026-30922 →CVE-2026-32597 →CVE-2024-34156 →CVE-2026-4599 →CVE-2026-4600 →CVE-2026-4601 →CVE-2026-4602 →CVE-2026-26996 →CVE-2026-28498 →CVE-2026-29063 →CVE-2024-45337 →CVE-2024-45338 →CVE-2025-61726 →CVE-2025-61728 →CVE-2025-68158 →CVE-2026-4598 →CVE-2026-25639 →CVE-2026-27904 →CVE-2025-61729 →CVE-2026-26007 →CVE-2026-27628 →CVE-2026-29074 →CVE-2025-68121 →CVE-2025-69873 →

📋 Description

CVE-2024-34156 — encoding/gob: golang: Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion CVE-2024-45337 — golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto CVE-2024-45338 — golang.org/x/net/html: Non-linear parsing of case-insensitive content in golang.org/x/net/html CVE-2025-61726 — golang: net/url: Memory exhaustion in query parameter parsing in net/url CVE-2025-61728 — golang: archive/zip: Excessive CPU consumption when building archive index in archive/zip CVE-2025-61729 — crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate CVE-2025-68121 — crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption CVE-2025-68158 — Authlib: Authlib: Cross-Site Request Forgery due to improper session management in state storage CVE-2025-69873 — ajv: ReDoS via $data reference CVE-2026-4598 — jsrsasign: jsrsasign: Denial of Service via infinite loop in bnModInverse function with crafted inputs CVE-2026-4599 — jsrsasign: jsrsasign: Private key recovery via incomplete comparison checks biasing DSA nonces CVE-2026-4600 — jsrsasign: jsrsasign: Cryptographic signature forgery via malicious DSA domain parameters CVE-2026-4601 — jsrsasign: jsrsasign: Private Key Recovery via Missing Cryptographic Step in DSA Signing CVE-2026-4602 — jsrsasign: jsrsasign: Signature verification bypass via negative exponent handling CVE-2026-25639 — axios: Axios affected by Denial of Service via proto Key in mergeConfig CVE-2026-25990 — pillow: Pillow: Out-of-bounds Write via Specially Crafted PSD Image CVE-2026-26007 — cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves CVE-2026-26996 — minimatch: minimatch: Denial of Service via specially crafted glob patterns CVE-2026-27628 — pypdf: possible infinite loop when loading circular /Prev entries in cross-reference streams CVE-2026-27904 — minimatch: Minimatch: Denial of Service via catastrophic backtracking in glob expressions CVE-2026-28498 — authlib: Authlib: Authentication bypass via forged OpenID Connect ID Tokens CVE-2026-28802 — authlib: Authlib: Signature verification bypass via malicious JWT allows unauthorized access CVE-2026-29063 — immutable-js: Immutable.js: Arbitrary code execution via Prototype Pollution CVE-2026-29074 — svgo: SVGO: Denial of Service via XML entity expansion CVE-2026-30922 — pyasn1: pyasn1 Vulnerable to Denial of Service via Unbounded Recursion CVE-2026-32597 — pyjwt: PyJWT accepts unknown crit header extensions (RFC 7515 §4.1.11 MUST violation)

🎯 Affected products23

  • Red Hat Quay 3.15
  • registry.redhat.io/quay/clair-rhel8@sha256:0a1c4f139b35d13aa4b3f6508919e25d3bbfdf588337704c1fc8cc7085bc2eb2_s390x as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/clair-rhel8@sha256:35047410a723f6e5b71137b7c6de497eed464dc1528419645cb308f2fd0696d6_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/clair-rhel8@sha256:76c0db9a4d4fcb45502d9d852f23a96aee91990217e19b519f7608eeb377eb22_ppc64le as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-bridge-operator-bundle@sha256:ebdb8e8b383adc86e78fbed0937c27bead67d0b6cb897a93c1558fd265696a1b_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:88854cbe000c3d84ee1000f1d350332eb861a031ece1e1ce0a4f85bcd1eb584e_ppc64le as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:a1d9c6f2f614dcea14f3b4564e69fe9ca894c9498fd08c5fdaa3616768ccedc3_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:d6ab62eec5e5489daa85fdda283e86c96101f7d576432d5a4b2865e4fdb0dbf1_s390x as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-builder-qemu-rhcos-rhel8@sha256:7b129e1319cc2f0edb134149b2cfecc021ca552cfede24d74d4631c3019e233e_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:2970429dcb7f99abf0d0cef4fa59346c90f129ae46d6e746d128b13e55616e06_ppc64le as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:5c02fe25ab73d531f543a673997170b5079c59c93e6ea240e795bfe6520782e3_s390x as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:9d81c106c68fab8c44dcd4c14698be0b8c76862885483ae20c5aa83c8334c805_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-container-security-operator-bundle@sha256:25b0676b9bb2e564fc64b43567ca4e3acda0a9d6ea405f2f8134b0e36b27b701_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:3681b3bb7257b54ea71d65370158e52d7165cc1038c129ea0266af21a773a022_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:cde4dc0f20b553550d6009ebc105e5cc80fbdd21d200f3d63f6c435f4addd804_ppc64le as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:ee7bf66cbb9116521d74e87d5a1b260bcce7634100aab7602149ad2c5bed4c72_s390x as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-operator-bundle@sha256:dec2520d12b13cd73ebceb03a82daddfff4b06e57e993268ea52cd21c0136147_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:26a62adcd46e5f84dff66336ccf9392a5bb8369b042dd01c3528ade17c6efa55_amd64 as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:8429e68dd8a1f4dc768304d17cd61beb772c0bcf5a4137d626b0a7333204d116_s390x as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:e5da14b11a892cc6cad89703d6415b95a47065fa2b1eb308c395579e9cce392a_ppc64le as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-rhel8@sha256:8acebb6bd51def60517b03f92103cecfadfc8e7fce42e4a002cb9c9271915b6b_ppc64le as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-rhel8@sha256:be166b843cc21b3942850443c0f802406f397f71959654a45e17a24fdcb0606a_s390x as a component of Red Hat Quay 3.15
  • registry.redhat.io/quay/quay-rhel8@sha256:c72dd9dd58db8ebcdc9b4daa433840411636e3dea82b21ca191fd0d272e636ec_amd64 as a component of Red Hat Quay 3.15

✅ Remediation

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 Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible. Workaround: To mitigate this vulnerability, implement a timeout in your archive/zip processing logic to abort the operation if it exceeds a few seconds, preventing the application from consuming an excessive amount of resources. 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: To mitigate this issue, disable the $data feature if your application does not require it. If $data must be used, implement strict validation of the input fields that are referenced by the pattern keyword to ensure they contain only expected and safe characters. 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.

🔗 References (29)