CVE-2026-49008

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-07. a secondary CVSS source baseline 6.5; sources differ by 0.0.

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

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

By accessing unencrypted information in the device firmware, an attacker can obtain credentials related to the integrity verification of a specific application function on the device.

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

Published

August 7, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

ZTE Corporation

https://support.zte.com.cn/zte-iccp-isupport-webui/bulletin/detail/2171542593031803093

Vendor Advisories for CVE-2026-49008(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 21× in last 7d / 43× 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-08-20 23:17 UTCEG score recompute
  2. 2026-08-20 23:17 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 22:46 UTCEG score recompute
  5. 2026-08-19 22:46 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 22:14 UTCEG score recompute
  8. 2026-08-18 22:14 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 21:38 UTCEG score recompute
  11. 2026-08-17 21:38 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 21:07 UTCEG score recompute
  14. 2026-08-16 21:07 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 20:36 UTCEG score recompute
  18. 2026-08-15 20:36 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 20:04 UTCEG score recompute
  21. 2026-08-14 20:04 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 19:32 UTCGHSA enrichment
  24. 2026-08-12 19:00 UTCEG score recompute
  25. 2026-08-12 19:00 UTCGHSA enrichment
Show 18 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 18:29 UTCEG score recompute
  3. 2026-08-11 18:29 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 17:58 UTCGHSA enrichment
  6. 2026-08-09 17:26 UTCEG score recompute
  7. 2026-08-09 17:26 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 16:55 UTCEG score recompute
  10. 2026-08-08 16:55 UTCGHSA enrichment
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 16:23 UTCEG score recompute
  13. 2026-08-07 16:23 UTCGHSA enrichment
  14. 2026-08-07 15:23 UTCEG score recompute
  15. 2026-08-07 15:23 UTCGHSA enrichment
  16. 2026-08-07 09:22 UTCEG score recompute
  17. 2026-08-07 08:33 UTCEG score recompute
  18. 2026-08-07 08:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49008?
CVE-2026-49008 is a medium vulnerability published on August 7, 2026. By accessing unencrypted information in the device firmware, an attacker can obtain credentials related to the integrity verification of a specific application function on the device.
When was CVE-2026-49008 disclosed?
CVE-2026-49008 was first published in the National Vulnerability Database on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49008 actively exploited?
CVE-2026-49008 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 92.8% of all scored CVEs.
What is the CVSS score of CVE-2026-49008?
CVE-2026-49008 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-49008?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49008, 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-49008

Explore →

Is Your Infrastructure Affected by CVE-2026-49008?

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

Start Free Scan →Browse All CVEs