CVE-2026-32591

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

April 8, 2026

Last Modified

August 24, 2026

Advisory Details (3)

Auto-updated May 20, 2026
Patch available. Sources: redhat.
redhat

2446965 – (CVE-2026-32591) CVE-2026-32591 mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration

https://bugzilla.redhat.com/show_bug.cgi?id=2446965
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-32591
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19375

Vendor Advisories for CVE-2026-32591(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel9:17849872732026-07-29redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat
redhatquay/quay-rhel9:17806040332026-06-09redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 243 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-09-01 04:39 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 14:17 UTCEPSS rescore
  13. 2026-08-24 12:27 UTCEG score recompute
  14. 2026-08-24 12:27 UTCVendor advisory
  15. 2026-08-24 12:27 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-19 17:03 UTCEPSS rescore
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 12:20 UTCVendor advisory
  24. 2026-08-17 12:20 UTCGHSA enrichment
  25. 2026-08-17 12:13 UTCEG score recompute
Show 75 more
  1. 2026-08-17 12:13 UTCVendor advisory
  2. 2026-08-17 12:13 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 22:29 UTCVendor advisory
  6. 2026-08-15 22:29 UTCGHSA enrichment
  7. 2026-08-15 21:33 UTCEG score recompute
  8. 2026-08-15 21:33 UTCVendor advisory
  9. 2026-08-15 21:33 UTCGHSA enrichment
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 05:16 UTCEG score recompute
  12. 2026-08-14 05:16 UTCVendor advisory
  13. 2026-08-14 05:16 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-12 12:38 UTCVendor advisory
  17. 2026-08-12 12:38 UTCGHSA enrichment
  18. 2026-08-12 12:13 UTCVendor advisory
  19. 2026-08-12 12:13 UTCGHSA enrichment
  20. 2026-08-11 22:20 UTCVendor advisory
  21. 2026-08-11 22:20 UTCGHSA enrichment
  22. 2026-08-11 21:25 UTCVendor advisory
  23. 2026-08-11 21:25 UTCGHSA enrichment
  24. 2026-08-11 19:46 UTCEG score recompute
  25. 2026-08-11 19:46 UTCVendor advisory
  26. 2026-08-11 19:46 UTCGHSA enrichment
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 12:27 UTCVendor advisory
  29. 2026-08-10 12:27 UTCGHSA enrichment
  30. 2026-08-10 05:25 UTCEG score recompute
  31. 2026-08-10 05:25 UTCVendor advisory
  32. 2026-08-10 05:25 UTCGHSA enrichment
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 04:44 UTCEG score recompute
  35. 2026-08-09 04:44 UTCVendor advisory
  36. 2026-08-09 04:44 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-07 14:41 UTCEG score recompute
  39. 2026-08-07 14:41 UTCVendor advisory
  40. 2026-08-07 14:41 UTCGHSA enrichment
  41. 2026-08-06 13:46 UTCEPSS rescore
  42. 2026-08-06 12:34 UTCVendor advisory
  43. 2026-08-06 12:34 UTCGHSA enrichment
  44. 2026-08-05 23:51 UTCEG score recompute
  45. 2026-08-05 23:51 UTCVendor advisory
  46. 2026-08-05 23:51 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:38 UTCEPSS rescore
  50. 2026-08-03 12:49 UTCEG score recompute
  51. 2026-08-03 12:49 UTCVendor advisory
  52. 2026-08-03 12:49 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 14:05 UTCEG score recompute
  55. 2026-08-02 14:05 UTCVendor advisory
  56. 2026-08-02 14:05 UTCGHSA enrichment
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 04:16 UTCEPSS rescore
  59. 2026-07-30 16:28 UTCEPSS rescore
  60. 2026-07-30 12:25 UTCVendor advisory
  61. 2026-07-30 12:25 UTCGHSA enrichment
  62. 2026-07-30 12:09 UTCEG score recompute
  63. 2026-07-30 12:09 UTCVendor advisory
  64. 2026-07-30 12:09 UTCGHSA enrichment
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-29 18:31 UTCVendor advisory
  67. 2026-07-29 18:31 UTCGHSA enrichment
  68. 2026-07-29 18:02 UTCEG score recompute
  69. 2026-07-29 18:02 UTCVendor advisory
  70. 2026-07-29 18:02 UTCGHSA enrichment
  71. 2026-07-27 14:13 UTCEPSS rescore
  72. 2026-07-27 12:40 UTCEG score recompute
  73. 2026-07-27 12:40 UTCVendor advisory
  74. 2026-07-27 12:40 UTCGHSA enrichment
  75. 2026-07-26 14:54 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32591?
CVE-2026-32591 is a medium vulnerability published on April 8, 2026. 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…
When was CVE-2026-32591 disclosed?
CVE-2026-32591 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32591 actively exploited?
CVE-2026-32591 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.9% of all scored CVEs.
What is the CVSS score of CVE-2026-32591?
CVE-2026-32591 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-32591?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32591, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-32591

Explore →

Is Your Infrastructure Affected by CVE-2026-32591?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs