CVE-2026-41981

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

Out-of-bounds write vulnerability in the IPC module. Impact: Successful exploitation of this vulnerability may affect availability.

CVSS v3
5.3
EG Score
5.3(medium)
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
0.1%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

Security Bulletins for HUAWEI Smart Watches, June 2026

https://consumer.huawei.com/en/support/bulletinwearables/2026/6/
generic

Security Bulletins for HUAWEI Phones/Tablets, June 2026

https://consumer.huawei.com/en/support/bulletin/2026/6/

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41981?
CVE-2026-41981 is a medium vulnerability published on June 9, 2026. Out-of-bounds write vulnerability in the IPC module. Impact: Successful exploitation of this vulnerability may affect availability.
When was CVE-2026-41981 disclosed?
CVE-2026-41981 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41981 actively exploited?
CVE-2026-41981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41981?
CVE-2026-41981 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-41981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41981, 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-41981

Explore →

Is Your Infrastructure Affected by CVE-2026-41981?

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

Start Free Scan →Browse All CVEs