CVE-2026-56220

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
6.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists Capgo versions before 12.128.2 as affected, and Capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

Capgo before 12.128.2 contains an authorization bypass vulnerability in the public.manifest INSERT policy that allows read-only org members to insert OTA manifest rows. Attackers with read-only org access can inject malicious manifest entries with arbitrary s3_path values that are served to devices via the unauthenticated /updates endpoint, enabling OTA metadata poisoning and potential malicious asset delivery.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (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

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
No fix on record yet. Sources: github.
Web page

Capgo - Unauthorized Manifest Insertion via Read-Only Org Member | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-unauthorized-manifest-insertion-via-read-only-org-member
GitHub advisoryMentions a patch (unverified)

Read-only org member can insert public.manifest rows and poison /updates manifest download URLs · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-vmgg-crr8-887p

Vendor Advisories for CVE-2026-56220(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-56220?
CVE-2026-56220 is a medium-severity vulnerability; its CVE record was published on July 8, 2026. Capgo before 12.128.2 contains an authorization bypass vulnerability in the public.manifest INSERT policy that allows read-only org members to insert OTA manifest rows. Attackers with read-only org access can inject malicious manifest entries with arbitrary s3_path values that are served to devices…
When was CVE-2026-56220 made public?
CVE-2026-56220 was made public on May 7, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 8, 2026; the record at its source may have been updated since.
Is CVE-2026-56220 actively exploited?
CVE-2026-56220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56220?
CVE-2026-56220 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56220?
No fix for CVE-2026-56220 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists Capgo versions before 12.128.2 as affected, and Capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-56220 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56220?

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