CVE-2026-32591
What it is
A flaw was found in Red Hat Quay's Proxy Cache configuration feature. When an organization administrator configures an upstream registry for proxy caching, Quay makes a network connection to the specified registry hostname without verifying that it points to a legitimate external service. An attacker with organization administrator privileges could supply a crafted hostname to force the Quay server to make requests to internal network services, cloud infrastructure endpoints, or other resources that should not be accessible from the Quay application.
At a glance
- Exploitability
- Can be exploited over the network with an admin-level account, but needs a user to act. High risk of data exposure.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.2 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-918 · Server-side request forgery
- Record status
- Modified
Affected
- Redhat Mirror Registry For Red Hat Openshift
- Redhat Mirror Registry For Red Hat Openshift 2.0
- Redhat Quay 3.0.0
Attack profile CVSS 3.1 · 5.2
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-32591.md and follow it. Check whether this project is affected by CVE-2026-32591. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://access.redhat.com/security/cve/CVE-2026-32591
- https://bugzilla.redhat.com/show_bug.cgi?id=2446965
- https://access.redhat.com/security/cve/CVE-2026-32591
- https://bugzilla.redhat.com/show_bug.cgi?id=2446965
References
- https://access.redhat.com/errata/RHSA-2026:24833
- https://access.redhat.com/errata/RHSA-2026:40262
- https://access.redhat.com/errata/RHSA-2026:41031
- https://access.redhat.com/errata/RHSA-2026:41066
- https://access.redhat.com/errata/RHSA-2026:42146
- https://access.redhat.com/errata/RHSA-2026:42796
- https://access.redhat.com/errata/RHSA-2026:43052
- https://access.redhat.com/errata/RHSA-2026:48085
- https://access.redhat.com/errata/RHSA-2026:70267
- https://access.redhat.com/security/cve/CVE-2026-32591
- https://bugzilla.redhat.com/show_bug.cgi?id=2446965
- https://access.redhat.com/errata/RHSA-2026:24833
- https://access.redhat.com/errata/RHSA-2026:40262
- https://access.redhat.com/errata/RHSA-2026:41031
- https://access.redhat.com/errata/RHSA-2026:41066
- https://access.redhat.com/errata/RHSA-2026:42146
- https://access.redhat.com/errata/RHSA-2026:42796
- https://access.redhat.com/errata/RHSA-2026:43052
- https://access.redhat.com/errata/RHSA-2026:48085
- https://access.redhat.com/security/cve/CVE-2026-32591
- https://bugzilla.redhat.com/show_bug.cgi?id=2446965
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32591.json