Red Hat Security Advisory: Red Hat Quay 3.10.18
Affects Red HatSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited.
Data as of 26 Oct 2026, 10:12 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Product Security Red Hat | Affected
| Fixed in– |
AI-suggested
Red Hat has released Quay 3.10.18 containing fixes for this issue and recommends applying this update along with all previously released errata relevant to the system. Currently, no direct mitigation for the underlying Go encoding/gob package flaw meets Red Hat's criteria for ease of use, applicability, or stability. Users should monitor Red Hat advisories for future updates and apply them promptly. No additional mitigations are specified by Red Hat at this time.
Description
Quay 3.10.18
References
- access.redhat.com/errata/RHSA-2026:2762 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2024-34156 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2024-45337 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2024-45338 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-12816 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-15284 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-52881 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-61729 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-65945 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-66031 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-66418 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-66471 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-66506 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-21441 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-24049 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_2762.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2025:3773 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2310528 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_3773.json (opens in a new tab)