RHSA-2026:5665HighCVSS 9.1

Red Hat Security Advisory: Red Hat Quay 3.10.19

Published
March 24, 2026
Last Modified
August 20, 2026

🔗 CVE IDs covered (12)

CVE-2025-61726 →CVE-2025-61728 →CVE-2025-68121 →CVE-2026-25639 →CVE-2026-26007 →CVE-2026-26996 →CVE-2026-27628 →CVE-2026-27962 →CVE-2026-25990 →CVE-2026-27606 →CVE-2026-27904 →CVE-2026-28802 →

📋 Description

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-68121 — crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption 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-27606 — rollup: Rollup: Remote Code Execution via Path Traversal Vulnerability 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-27962 — authlib: Authlib: Authentication bypass due to JWK Header Injection vulnerability CVE-2026-28802 — authlib: Authlib: Signature verification bypass via malicious JWT allows unauthorized access

🎯 Affected products23

  • Red Hat Quay 3.1
  • registry.redhat.io/quay/clair-rhel8@sha256:733de3a7351b69265aee8d12c7fe65f60e099c923510758a75c8800409126c41_ppc64le as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/clair-rhel8@sha256:caa20d6002cfd42dc4ab86dee5dde07da0a7e1dcc310c9be33bf28a2df1ef82b_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/clair-rhel8@sha256:d59935575d41174ccd39a7d7610b44d7e6afa0f56041bdefa40bc7ad4e1c837f_s390x as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-bridge-operator-bundle@sha256:042530fcf03002da68993546ee82f483f387bd09ffe5fefaad9344b80ee842b1_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:3fb6c2af69237c3ff2cd326bc655028392a2d11c9162b85a9c4a762cbe7d044b_ppc64le as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:4d88d159b8a0e46a8508735f555179c6b08caef62d42e5fb676fdac10e333f58_s390x as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:fe1c94521b952469093c28ca9805c6758b4ac2ec6e3aa2a2001645e304949a21_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-builder-qemu-rhcos-rhel8@sha256:443977ffd46161f026a30edfb8735139b7c430ca7b054b71ada75fc251226c99_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:5558d6af86f65a79c88f1ffe290b49219d0f00c93ec8a03f0e81d0e9e13501fc_s390x as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:9e96b505901615f671d5b99094bda544ecbce32a3772125f2baf5f0ea67d5687_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:ba56dd8ef744ea12e21ade86c91a9faca072e39256f98edd677a419eeae8e7a0_ppc64le as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-container-security-operator-bundle@sha256:7e7559212648d972eec26d27cad42b1f93fefcc61c6ab884a730a48c81574734_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:6bf4ab153aa99b67b1e3fe0cbf0fa3e3694d3394c957fc03a5578d03cb2e88bc_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:720000552d67523e437f0638abf185ae32040f1437225fc461be499490494ce7_ppc64le as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:edd76ba97d059e00755472146df0c84ff441c77e7cea12b9f5cd460f0c30e942_s390x as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-operator-bundle@sha256:e165eed009ce74a4ad2de04ff1cbbcf9eabb3900bef6de3dd2483e484e9e10b3_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:0731cf4122bec0cef7c4f05ee19fe43871d977515c91e0decce981abeab85af6_ppc64le as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:0c8ad49237e784b6bcaf48c62928533a231026b1605926edee0313d3a83c10c4_s390x as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:de004a925cd7fdae3ba4698165c0a4e814607b6f33d2f7154c8d79b76c826dd7_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-rhel8@sha256:6e13793ca8f309ec0b69ae609b840ff0f41989d88cd4bba127e1b0040631367e_ppc64le as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-rhel8@sha256:c0d00643c4ac6f84e5327192a29c6353b5dcac34d483d0a3e5f39d366127fcc2_amd64 as a component of Red Hat Quay 3.1
  • registry.redhat.io/quay/quay-rhel8@sha256:f6a231ebb14c74e194a8091822fe6a981e1cec92d223e04e6d0f12b60206259a_s390x as a component of Red Hat Quay 3.1

✅ 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: 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 (15)