CVE-2026-49006

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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 TLS transmission.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
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/460175237240021109

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

Frequently asked(5)

What is CVE-2026-49006?
CVE-2026-49006 is a medium vulnerability published on August 7, 2026. By accessing unencrypted information in the device firmware, an attacker can obtain credentials related to TLS transmission.
When was CVE-2026-49006 disclosed?
CVE-2026-49006 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-49006 actively exploited?
CVE-2026-49006 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 95.5% of all scored CVEs.
What is the CVSS score of CVE-2026-49006?
CVE-2026-49006 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-49006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49006, 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-49006

Explore →

Is Your Infrastructure Affected by CVE-2026-49006?

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

Start Free Scan →Browse All CVEs