In gf_algo_get_cached_dump_data of gf_algo.c, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2026-56958
Score 5.5 from GitHub Security Advisory published 2026-09-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/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 computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 21, 2026
Advisory Details (1)
Auto-updated Sep 15, 2026Pixel Update Bulletin—September 2026 | Android Open Source Project
https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01Vendor Advisories for CVE-2026-56958(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 12× in last 7d / 24× 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.
- 2026-09-24 20:03 UTCEG score recompute
- 2026-09-24 20:03 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 19:20 UTCEG score recompute
- 2026-09-23 19:20 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 18:10 UTCEG score recompute
- 2026-09-22 18:10 UTCGHSA enrichment
- 2026-09-21 17:28 UTCGHSA enrichment
- 2026-09-20 22:40 UTCGHSA enrichment
- 2026-09-19 21:58 UTCGHSA enrichment
- 2026-09-18 21:15 UTCGHSA enrichment
- 2026-09-17 20:17 UTCEG score recompute
- 2026-09-17 20:17 UTCGHSA enrichment
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 19:34 UTCGHSA enrichment
- 2026-09-16 16:54 UTCEG score recompute
- 2026-09-16 16:54 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 20:35 UTCEG score recompute▲ 5.50
- 2026-09-15 20:27 UTCMITRE cvelistV5CVSS v3 → 5.5 · severity → MEDIUM
- 2026-09-15 19:32 UTCNVD update
- 2026-09-15 18:39 UTCEG score recompute
- 2026-09-15 18:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-56958?
When was CVE-2026-56958 disclosed?
Is CVE-2026-56958 actively exploited?
What is the CVSS score of CVE-2026-56958?
How do I remediate CVE-2026-56958?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56958
Is Your Infrastructure Affected by CVE-2026-56958?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.