Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2026-32591: Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit No fix recorded
Published
Apr 8, 2026
Updated
Nov 1, 2026
EPSS
0.3% · 25th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · redhat
5.2
0.3 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-32591

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for redhat records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
redhatmirror registry for red hat openshift
redhatquay

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat mirror registry for red hat openshiftall versions
  • redhat mirror registry for red hat openshift2.0
  • redhat quay3.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat mirror registry for Red Hat OpenShift

    • all versionsaffected

  • Red Hat mirror registry for Red Hat OpenShift 2

    • all versionsaffected

  • Red Hat Red Hat Quay 3.10

    • 1783750447 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.12

    • 1783751865 and laternot affected · rpm
    • 1784353904 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.14

    • 1788593843 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.15

    • 1784351966 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.16

    • 1783955846 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.17

    • 1780604033 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.18

    • 1784987273 and laternot affected · rpm

  • Red Hat Red Hat Quay 3.9

    • 1784125838 and laternot affected · rpm

Same product

redhat: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-32590Mirror-registry: remote code execution using pickle deserialization
    35Monitor
  • CVE-2026-32589Mirror-registry: quay: insecure direct object reference in blobupload
    29Monitor
  • CVE-2026-2377Mirror-registry: quay: quay: server-side request forgery via log export functionality
    26Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-14243Apr 8, 2026 · Mirror-registry: openshift mirror registry: user enumeration via authentication error messages
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-23770 days apartMirror-registry: quay: quay: server-side request forgery via log export functionality
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-918 · Server-Side Request Forgery (SSRF)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Show all references (11 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records