CVE-2026-1784

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-02. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

The Route OpenShift resource allows to define routes to make pods reachable at a subdomain through HAProxy. It was found that the checks performed on the spec.path YAML stanza in a Route document was insufficient and could allow a controlled injection of the HAProxy configuration.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 26, 2026

Advisory Details (2)

Auto-updated Jun 2, 2026
Patch available. Sources: redhat.
redhat

Bug Access Denied

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-1784

Vendor Advisories for CVE-2026-1784(9)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-cluster-ingress-operator:17818701012026-07-01redhat
redhatopenshift4/ose-cluster-ingress-rhel9-operator:17819288572026-07-01redhat
redhatopenshift4/ose-cluster-ingress-operator:17811230142026-06-25redhat
redhatopenshift4/ose-cluster-ingress-rhel9-operator:17809882802026-06-17redhat
redhatopenshift4/ose-cluster-ingress-rhel9-operator:17809626172026-06-17redhat
redhatopenshift4/ose-cluster-ingress-rhel9-operator:17809909772026-06-16redhat
redhatopenshift4/ose-cluster-ingress-rhel9-operator:17804443482026-06-11redhat
redhatopenshift4/ose-cluster-ingress-rhel9-operator:17800433382026-06-10redhat

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.

Data Freshness Timeline

(refreshed 20× in last 7d / 86× 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 188 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-1784?
CVE-2026-1784 is a high vulnerability published on June 2, 2026. The Route OpenShift resource allows to define routes to make pods reachable at a subdomain through HAProxy. It was found that the checks performed on the spec.path YAML stanza in a Route document was insufficient and could allow a controlled injection of the HAProxy configuration.
When was CVE-2026-1784 disclosed?
CVE-2026-1784 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1784 actively exploited?
CVE-2026-1784 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 90.6% of all scored CVEs.
What is the CVSS score of CVE-2026-1784?
CVE-2026-1784 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-1784?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1784, 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-1784

Explore →

Is Your Infrastructure Affected by CVE-2026-1784?

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

Start Free Scan →Browse All CVEs