CVE-2026-0056

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-06-02. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0

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

In setTo of ResourceTypes.cpp, there is a possible read out of bounds due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

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

Published

June 1, 2026

Last Modified

July 22, 2026

References (1)

Vendor Advisories for CVE-2026-0056(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 6× in last 7d / 15× 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.

  1. 2026-07-26 23:09 UTCEG score recompute
  2. 2026-07-26 23:09 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-24 14:17 UTCEPSS rescore
  6. 2026-07-23 03:04 UTCEG score recompute
  7. 2026-07-14 21:39 UTCGHSA enrichment
  8. 2026-07-11 18:20 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-08 16:50 UTCGHSA enrichment
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-06-30 04:22 UTCGHSA enrichment
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-27 03:07 UTCGHSA enrichment
  17. 2026-06-24 01:37 UTCGHSA enrichment
  18. 2026-06-20 13:39 UTCGHSA enrichment
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-17 03:20 UTCGHSA enrichment
  22. 2026-06-15 17:48 UTCEPSS rescore
  23. 2026-06-14 23:18 UTCEPSS rescore
  24. 2026-06-14 02:12 UTCGHSA enrichment
  25. 2026-06-11 14:00 UTCEPSS rescore
Show 17 more
  1. 2026-06-11 01:03 UTCGHSA enrichment
  2. 2026-06-10 22:18 UTCEPSS rescore
  3. 2026-06-10 13:22 UTCEPSS rescore
  4. 2026-06-07 23:55 UTCGHSA enrichment
  5. 2026-06-07 15:25 UTCEPSS rescore
  6. 2026-06-07 15:24 UTCEPSS rescore
  7. 2026-06-05 22:47 UTCEPSS rescore
  8. 2026-06-05 06:10 UTCEPSS rescore
  9. 2026-06-05 06:10 UTCEPSS rescore
  10. 2026-06-04 22:47 UTCEG score recompute▲ 3.30
  11. 2026-06-04 22:47 UTCGHSA enrichment
  12. 2026-06-04 13:12 UTCEPSS rescore
  13. 2026-06-04 13:12 UTCEPSS rescore
  14. 2026-06-04 13:12 UTCEPSS rescore
  15. 2026-06-02 20:13 UTCEPSS rescore
  16. 2026-06-02 20:13 UTCEPSS rescore
  17. 2026-06-01 21:38 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0056?
CVE-2026-0056 is a low vulnerability published on June 1, 2026. In setTo of ResourceTypes.cpp, there is a possible read out of bounds due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-0056 disclosed?
CVE-2026-0056 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0056 actively exploited?
CVE-2026-0056 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 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-0056?
CVE-2026-0056 has a CVSS v3.1 base score of 3.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0056?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0056, 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-0056

Explore →

Is Your Infrastructure Affected by CVE-2026-0056?

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

Start Free Scan →Browse All CVEs