CVE-2026-49313

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

Permission control vulnerability in the app lock module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

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

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

Security Bulletins for HUAWEI Phones/Tablets, September 2026

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

Vendor Advisories for CVE-2026-49313(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 11× in last 7d / 30× 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-20 19:25 UTCGHSA enrichment
  2. 2026-09-19 19:41 UTCEG score recompute
  3. 2026-09-19 19:41 UTCGHSA enrichment
  4. 2026-09-18 19:58 UTCGHSA enrichment
  5. 2026-09-17 20:15 UTCEG score recompute
  6. 2026-09-17 20:15 UTCGHSA enrichment
  7. 2026-09-16 19:37 UTCEG score recompute
  8. 2026-09-16 19:37 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-15 19:50 UTCGHSA enrichment
  11. 2026-09-14 20:05 UTCGHSA enrichment
  12. 2026-09-13 20:22 UTCEG score recompute
  13. 2026-09-13 20:22 UTCGHSA enrichment
  14. 2026-09-13 16:47 UTCEPSS rescore
  15. 2026-09-12 20:39 UTCGHSA enrichment
  16. 2026-09-11 20:56 UTCEG score recompute
  17. 2026-09-11 20:56 UTCGHSA enrichment
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-10 21:13 UTCEG score recompute
  20. 2026-09-10 21:13 UTCGHSA enrichment
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-09 21:30 UTCEG score recompute
  23. 2026-09-09 21:30 UTCGHSA enrichment
  24. 2026-09-09 20:55 UTCEG score recompute
  25. 2026-09-09 20:55 UTCGHSA enrichment
Show 5 more
  1. 2026-09-09 15:51 UTCEG score recompute
  2. 2026-09-09 15:51 UTCGHSA enrichment
  3. 2026-09-09 04:37 UTCEG score recompute
  4. 2026-09-09 04:02 UTCEG score recompute
  5. 2026-09-09 04:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49313?
CVE-2026-49313 is a medium vulnerability published on September 9, 2026. Permission control vulnerability in the app lock module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
When was CVE-2026-49313 disclosed?
CVE-2026-49313 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49313 actively exploited?
CVE-2026-49313 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 99.9% of all scored CVEs.
What is the CVSS score of CVE-2026-49313?
CVE-2026-49313 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-49313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49313, 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-49313

Explore →

Is Your Infrastructure Affected by CVE-2026-49313?

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

Start Free Scan →Browse All CVEs