CVE-2026-21075

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

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

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

Improper authorization in handler for custom URL scheme in My Galaxy prior to version 6.3 allows remote attackers to access sensitive information.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 18, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
No patch confirmed yet.
generic

Samsung Mobile Security

https://security.samsungmobile.com/serviceWeb.smsb?year=2026&month=08

Vendor Advisories for CVE-2026-21075(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 20× in last 7d / 37× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:50 UTCGHSA enrichment
  3. 2026-08-19 18:45 UTCEG score recompute
  4. 2026-08-19 18:45 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 15:34 UTCEG score recompute
  7. 2026-08-18 15:33 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 09:02 UTCEG score recompute
  10. 2026-08-18 09:01 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 06:55 UTCEG score recompute
  13. 2026-08-17 06:55 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 04:51 UTCEG score recompute
  16. 2026-08-16 04:51 UTCGHSA enrichment
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 02:46 UTCEG score recompute
  19. 2026-08-15 02:46 UTCGHSA enrichment
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 00:40 UTCEG score recompute
  22. 2026-08-14 00:40 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 22:35 UTCEG score recompute
  25. 2026-08-12 22:35 UTCGHSA enrichment
Show 12 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 20:30 UTCEG score recompute
  3. 2026-08-11 20:30 UTCGHSA enrichment
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 18:25 UTCEG score recompute
  7. 2026-08-10 18:25 UTCGHSA enrichment
  8. 2026-08-10 17:35 UTCEG score recompute
  9. 2026-08-10 17:35 UTCGHSA enrichment
  10. 2026-08-10 09:20 UTCEG score recompute
  11. 2026-08-10 08:16 UTCEG score recompute
  12. 2026-08-10 08:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-21075?
CVE-2026-21075 is a medium vulnerability published on August 10, 2026. Improper authorization in handler for custom URL scheme in My Galaxy prior to version 6.3 allows remote attackers to access sensitive information.
When was CVE-2026-21075 disclosed?
CVE-2026-21075 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21075 actively exploited?
CVE-2026-21075 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 70.7% of all scored CVEs.
What is the CVSS score of CVE-2026-21075?
CVE-2026-21075 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-21075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21075, 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-21075

Explore →

Is Your Infrastructure Affected by CVE-2026-21075?

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

Start Free Scan →Browse All CVEs