CVE-2026-50112

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

SSRF via Metalink Mirror URL Resolution:

An authenticated tenant can register a template pointing to an attacker-controlled metalink file containing internal targets. The Secondary Storage VM will retrieve the data and persist it as a template file, which can later be downloaded through normal APIs.

RCE on KVM hypervisor via NFS, Metalink files with/without Direct Downloads:

An authenticated CloudStack tenant holding the default User role can execute arbitrary shell commands as root on the KVM hypervisor host that runs other tenants' VMs. This is cross-tenant root on the underlying compute, reachable via the public CloudStack API.

When a User registers a VM template with directDownload=true and a URL pointing to a .metalink file, the management server fetches the metalink XML and dispatches download to the KVM agent. Inner URLs inside the metalink XML are never re-validated against the scheme allowlist.

These issues affect Apache CloudStack: from 4.14.0.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0.

Users are recommended to upgrade to version 4.20.3.1 or 4.22.1.1 or later, which fixes the issue.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.7% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 21, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Aug 21, 2026
Fix named in the CVE record.

Vendor Advisories for CVE-2026-50112(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 92× 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 186 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 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-50112?
CVE-2026-50112 is a high-severity vulnerability; its CVE record was published on August 21, 2026. SSRF via Metalink Mirror URL Resolution: An authenticated tenant can register a template pointing to an attacker-controlled metalink file containing internal targets. The Secondary Storage VM will retrieve the data and persist it as a template file, which can later be downloaded through normal…
When was the CVE record for CVE-2026-50112 published?
The CVE record for CVE-2026-50112 was published on August 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 27, 2026; the record at its source may have been updated since.
Is CVE-2026-50112 actively exploited?
CVE-2026-50112 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50112?
CVE-2026-50112 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-50112?
The CVE record for CVE-2026-50112 names the fix: "Users are recommended to upgrade to version 4.20.3.1 or 4.22.1.1 or later, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-50112 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50112?

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