CVE-2016-10408

HIGHNVD 8.48.4—

8.4

QSEE will randomly experience a fatal error during execution due to speculative instruction fetches from device memory. Device memory is not valid executable memory.

CVSS v3: 8.4
EG Score: 8.4(medium)
EPSS: 15.3%
KEV: Not listed

Published

November 26, 2024

Last Modified

January 9, 2025

References (1)

product-security@qualcommhttps://docs.qualcomm.com/product/publicresources/securitybulletin/may-2018-bulletin.html

Weakness Classification(1)

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

CWE-284Improper Access Control

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:43 UTCepss_batch
2026-05-23 17:19 UTCEG score recompute
2026-05-23 17:19 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2016-10408?

CVE-2016-10408 is a high vulnerability published on November 26, 2024. QSEE will randomly experience a fatal error during execution due to speculative instruction fetches from device memory. Device memory is not valid executable memory.

When was CVE-2016-10408 disclosed?

CVE-2016-10408 was first published in the National Vulnerability Database on November 26, 2024, with the most recent update on January 9, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2016-10408 actively exploited?

CVE-2016-10408 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2016-10408?

CVE-2016-10408 has a CVSS v3 base score of 8.4 (NVD).

How do I remediate CVE-2016-10408?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-10408, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-10408

Explore →

Is Your Infrastructure Affected by CVE-2016-10408?

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

Start Free Scan →Browse All CVEs

CVE-2016-10408

📅 Published

🔄 Last Modified

🔗 References (1)