CVE-2026-18874

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.2 from GitHub Security Advisory published 2026-08-19. A secondary CVSS source baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
6.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in volsync-addon-controller. This vulnerability allows an attacker to inject malicious YAML (Yet Another Markup Language) code into the OpenShift Lifecycle Manager (OLM) Subscription resource. This is due to improper escaping of annotation values when they are rendered into YAML. Successful exploitation could lead to unauthorized modification or control over OLM Subscription configurations, potentially impacting software management within the cluster. This issue primarily affects systems where the 'volsync-addon-deploy-type: olm' annotation is explicitly enabled.

CVSS v3
6.2
EG Score
6.2MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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 (value × EchelonGraph’s weight)
Severity62% × 45%
The EG Score, 6.2 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
Patch available. Sources: redhat.
Red Hat

2511115 – (CVE-2026-18874) CVE-2026-18874 volsync-addon-controller: volsync-addon-controller: annotation values rendered into YAML via text/template without escaping allows YAML injection into Subscription

https://bugzilla.redhat.com/show_bug.cgi?id=2511115
Red HatMentions a patch (unverified)

CVE-2026-18874 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

Vendor Advisories for CVE-2026-18874(7)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/acm-volsync-addon-controller-rhel9:17872663602026-08-26redhat
redhatrhacm2/acm-volsync-addon-controller-rhel9:17872665642026-08-26redhat
redhatrhacm2/acm-volsync-addon-controller-rhel9:17872665562026-08-26redhat
redhatrhacm2/acm-volsync-addon-controller-rhel9:17876835602026-08-26redhat

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 12× in last 7d / 80× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 193 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-18874?
CVE-2026-18874 is a medium-severity vulnerability; its CVE record was published on August 19, 2026. A flaw was found in volsync-addon-controller. This vulnerability allows an attacker to inject malicious YAML (Yet Another Markup Language) code into the OpenShift Lifecycle Manager (OLM) Subscription resource. This is due to improper escaping of annotation values when they are rendered into YAML.…
When was CVE-2026-18874 made public?
CVE-2026-18874 was made public on August 19, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-18874 actively exploited?
CVE-2026-18874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18874?
CVE-2026-18874 has a CVSS base score of 6.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18874?
A fix for CVE-2026-18874 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18874 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-18874?

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

Book a Demo →Browse All CVEs