CVE-2026-0010

HIGHNVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-03-02. NVD baseline CVSS 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

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

In onTransact of IDrmManagerService.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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

Published

March 2, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Jul 28, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

oss-security - [NotCVE-2026-0010] Barrier 2.4.0 for Windows Unauthenticated IPC Command Execution Allows Local Privilege Escalation to SYSTEM

http://www.openwall.com/lists/oss-security/2026/07/28/4
generic

Android Security Bulletin—March 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-03-01

Vendor Advisories for CVE-2026-0010(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 3× in last 7d / 22× 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-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 23:02 UTCEG score recompute
  9. 2026-09-08 23:02 UTCGHSA enrichment
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-28 21:40 UTCEPSS rescore
  17. 2026-08-27 14:24 UTCEPSS rescore
  18. 2026-08-26 19:23 UTCGHSA enrichment
  19. 2026-08-26 18:42 UTCEG score recompute
  20. 2026-08-26 18:42 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:48 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 38 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 21:02 UTCGHSA enrichment
  4. 2026-08-14 08:43 UTCGHSA enrichment
  5. 2026-08-13 00:33 UTCGHSA enrichment
  6. 2026-08-11 23:24 UTCEG score recompute
  7. 2026-08-11 23:23 UTCGHSA enrichment
  8. 2026-08-11 13:42 UTCEPSS rescore
  9. 2026-08-11 05:57 UTCEG score recompute
  10. 2026-08-11 05:57 UTCGHSA enrichment
  11. 2026-08-10 23:59 UTCEPSS rescore
  12. 2026-08-10 08:01 UTCGHSA enrichment
  13. 2026-08-09 19:10 UTCEG score recompute
  14. 2026-08-09 19:10 UTCGHSA enrichment
  15. 2026-08-09 13:46 UTCEPSS rescore
  16. 2026-08-09 08:20 UTCEG score recompute
  17. 2026-08-09 08:20 UTCGHSA enrichment
  18. 2026-08-08 16:37 UTCEPSS rescore
  19. 2026-08-08 07:07 UTCGHSA enrichment
  20. 2026-08-07 20:16 UTCEG score recompute
  21. 2026-08-07 20:16 UTCGHSA enrichment
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 02:50 UTCEG score recompute
  24. 2026-08-06 02:50 UTCGHSA enrichment
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-04 15:09 UTCEPSS rescore
  27. 2026-08-04 04:35 UTCGHSA enrichment
  28. 2026-08-02 19:10 UTCEG score recompute
  29. 2026-08-02 19:10 UTCGHSA enrichment
  30. 2026-08-01 04:15 UTCEPSS rescore
  31. 2026-07-30 16:27 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-28 15:36 UTCEPSS rescore
  34. 2026-07-28 08:20 UTCEG score recompute
  35. 2026-07-28 08:20 UTCGHSA enrichment
  36. 2026-07-27 14:13 UTCEPSS rescore
  37. 2026-07-27 13:56 UTCEG score recompute
  38. 2026-07-27 13:56 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0010?
CVE-2026-0010 is a high vulnerability published on March 2, 2026. In onTransact of IDrmManagerService.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-0010 disclosed?
CVE-2026-0010 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0010 actively exploited?
CVE-2026-0010 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-0010?
CVE-2026-0010 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-0010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0010, 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-0010

Explore →

Is Your Infrastructure Affected by CVE-2026-0010?

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

Start Free Scan →Browse All CVEs