Permission control vulnerability in the event notification module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
CVE-2026-49310
Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. a secondary CVSS source baseline 8.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(high)
- EG Risk
- 54(Track)EG Risk 54/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 computedSeverity86% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 9, 2026
Advisory Details (4)
Auto-updated Sep 9, 2026Security Bulletins for HUAWEI PCs, September 2026
https://consumer.huawei.com/en/support/bulletinlaptops/2026/9/Security Bulletins for HUAWEI Smart Watches, September 2026
https://consumer.huawei.com/en/support/bulletinwearables/2026/9/Security Bulletins for HUAWEI Vision, September 2026
https://consumer.huawei.com/en/support/bulletinvision/2026/9/Security Bulletins for HUAWEI Phones/Tablets, September 2026
https://consumer.huawei.com/en/support/bulletin/2026/9/Vendor Advisories for CVE-2026-49310(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 24× in last 7d / 48× 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.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 18:50 UTCGHSA enrichment
- 2026-09-20 07:04 UTCGHSA enrichment
- 2026-09-19 19:18 UTCEG score recompute
- 2026-09-19 19:18 UTCGHSA enrichment
- 2026-09-19 07:32 UTCGHSA enrichment
- 2026-09-18 19:47 UTCEG score recompute
- 2026-09-18 19:47 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 08:01 UTCGHSA enrichment
- 2026-09-17 20:15 UTCEG score recompute
- 2026-09-17 20:15 UTCGHSA enrichment
- 2026-09-17 06:00 UTCGHSA enrichment
- 2026-09-16 18:12 UTCEG score recompute
- 2026-09-16 18:12 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 06:26 UTCEG score recompute
- 2026-09-16 06:26 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 18:41 UTCGHSA enrichment
- 2026-09-15 06:54 UTCEG score recompute
- 2026-09-15 06:54 UTCGHSA enrichment
- 2026-09-14 19:08 UTCGHSA enrichment
- 2026-09-14 07:22 UTCGHSA enrichment
- 2026-09-13 19:37 UTCEG score recompute
Show 23 moreShow fewer
- 2026-09-13 19:37 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 07:51 UTCGHSA enrichment
- 2026-09-12 20:06 UTCEG score recompute
- 2026-09-12 20:06 UTCGHSA enrichment
- 2026-09-12 08:19 UTCGHSA enrichment
- 2026-09-11 20:34 UTCEG score recompute
- 2026-09-11 20:34 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 08:48 UTCGHSA enrichment
- 2026-09-10 21:02 UTCEG score recompute
- 2026-09-10 21:02 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 09:16 UTCGHSA enrichment
- 2026-09-09 21:30 UTCEG score recompute
- 2026-09-09 21:30 UTCGHSA enrichment
- 2026-09-09 20:55 UTCEG score recompute
- 2026-09-09 20:55 UTCGHSA enrichment
- 2026-09-09 15:52 UTCEG score recompute
- 2026-09-09 15:51 UTCGHSA enrichment
- 2026-09-09 04:38 UTCEG score recompute
- 2026-09-09 03:32 UTCEG score recompute
- 2026-09-09 03:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-264
- CVE-2025-5321EG 9.9CRITICAL
- CVE-2022-36246EG 9.8CRITICAL
- CVE-2022-41781NVD 6.5EG 9.8CRITICAL
- CVE-2022-37344NVD 7.6EG 9.8CRITICAL
- CVE-2022-36427NVD 7.3EG 9.8CRITICAL
- CVE-2022-36387NVD 7.6EG 9.8CRITICAL
- CVE-2022-36425NVD 5.4EG 9.8CRITICAL
- CVE-2022-34149EG 9.8CRITICAL
- CVE-2022-34487EG 9.8CRITICAL
- CVE-2022-33198EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-49310?
When was CVE-2026-49310 disclosed?
Is CVE-2026-49310 actively exploited?
What is the CVSS score of CVE-2026-49310?
How do I remediate CVE-2026-49310?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-49310
Is Your Infrastructure Affected by CVE-2026-49310?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.