RHSA-2025:23059HighCVSS 7.5

Red Hat Security Advisory: Red Hat Quay 3.12

Published
December 10, 2025
Last Modified
August 23, 2026

🔗 CVE IDs covered (4)

CVE-2024-34156 →CVE-2025-47913 →CVE-2025-59420 →CVE-2025-61920 →

📋 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-2025-47913 — golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: SSH client panic due to unexpected SSH_AGENT_SUCCESS CVE-2025-59420 — authlib: Authlib RFC violation CVE-2025-61920 — authlib: Authlib Denial of Service

🎯 Affected products32

  • Red Hat Quay 3.12
  • registry.redhat.io/quay/clair-rhel8@sha256:11091b652f65868606c3d4d3e30a04cea7396f06f119bcd0a4cf664db2aa790e_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/clair-rhel8@sha256:212ceac279067567409c47acf7792e0c4d1955395f045e3b717040321dc1b88f_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/clair-rhel8@sha256:451da4b858587adcef52b5f1c9b7c92985bd7cc7c90f651b9e38825b81b38fb0_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/clair-rhel8@sha256:c5cb9d3d0f970ad36005f2d376547e967e4a89574cca1cf8806bb92d05199d70_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-bridge-operator-bundle@sha256:0a978bbe91e0e0b8bab6862522f8a0aa8e974b778cc36b83f0781081621c8e23_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:8b3684c92affc7acadcd5dc8eb80e5727081c7ecf4cc6eeafe5ecc5ea60970bb_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:8d474498354d438fc9deeceb3bc89649f35d4e382e930ee721059bfeaf0f8279_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:ad2119941c2e8db1691a9bfee085425c7203ab00c2cdf0a6441b1102109cfd21_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-bridge-operator-rhel8@sha256:cdf96fe7a1ad4c192b4313e804d40d5c656c3f0ced498bae2427e449f0b2df02_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-qemu-rhcos-rhel8@sha256:0c7a94928e8ef89aebdd9b30a47aaf0fe4dfb3a716603362b5c7d52255c4e842_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-qemu-rhcos-rhel8@sha256:1f769259f2b91d47f4d4fbf92414903a62380a358737e7100a1166ccd8c89b85_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-qemu-rhcos-rhel8@sha256:a71b5493009863c4f1e9ae9393ff236dc262d84ee028482ee58840fbfe392c83_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-qemu-rhcos-rhel8@sha256:bd796d2de4d02f63adc767aa22b9a388b3adea40c12b0d8f158ebffabed6fee9_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:00eb13b3cccf326292589a680a964160c58f83391d0036c4ebcb34fad32b6189_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:0ca5a583ca7ff0161ed35deeae94be78adc74100d0343b778f1edf5b77e90925_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:3facbc804376b505181c2f52f0c7a433111bcedcb5699a0fcdffd7e9a2bdfbbe_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-builder-rhel8@sha256:7a338bb18181535a2644bf70cae05042e1ef2af5a80e70a6cab6516e8f054896_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-container-security-operator-bundle@sha256:53c387293b92691eb66ea73b1d29781cf275f01b4254c38e21620c0502987272_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:1b0a31b5f6d1e1493974efb8c7ca5112e6e4d8f0b8e1de8e55b7b8c1184b2293_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:33d0912dbad0b1702fd91abf87e38910d2b983334062044c292a0cb1714187a0_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:7814f04947e8e98d3c4870894e320b12c557976495bdf28a89b55bf061bacf79_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-container-security-operator-rhel8@sha256:b2a263d3cbf303d0dffb2c36ee2a4187c29902ce96ca1ded6f33b2edcc68fda9_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-operator-bundle@sha256:1c915a6f813564b9bf8062ea5c6a83097a8dd78a38fda0171fae9cc8d81299c7_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:37039569fe73c3975468ffb8640c42becdd9b5304fb5e54789bf59dc67c52c9b_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:4e2ef7cca978574e1715c24b9874c7a0a1a46a6319884a91fe54df06efe97df1_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:b2e2d245c7ba3d1528e73b59bad428f023eeb17a1983d61edcf6a22db58911cf_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-operator-rhel8@sha256:f960e1816f8babb590a55ccab9f2db1b567df749e73c70067269d32f6200bca6_amd64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-rhel8@sha256:30152d31da209c034ec39b52a32063437097eec9a4fac2eaf4a4110fea97cb70_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-rhel8@sha256:38f094f62eed92d88eae0e7a9be410ef908bd0194b30240d49087ae76250e0ee_ppc64le as a component of Red Hat Quay 3.12
  • +2 more not shown

✅ 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: No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, 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. Workaround: Users unable to upgrade may manually enforce input size limits before handing tokens to Authlib and/or use application-level throttling to reduce amplification risk.

🔗 References (7)