MobSF is a mobile application security testing tool used. Prior to 4.5.1, get_browsable_activities in mobsf/StaticAnalyzer/views/android/manifest_analysis.py validates only an Android manifest android:host value with valid_host before appending a separately supplied android:port to the URL fetched by _check_url, allowing an authenticated user to upload a crafted APK that makes requests to an attacker-selected nonstandard port at /.well-known/assetlinks.json. With an attacker-controlled hostname and DNS rebinding between validation and the requests.get connection, the request can reach an internal service, although redirects remain disabled and the path is fixed. This issue is fixed in version 4.5.1.
CVE-2026-68927
LOWPre-NVD 3.03.0Trending — 3 sources updated this weekElevated
EchelonGraph scoreLOW confidence
This low-severity CVE scores 3.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
3.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.0Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.0
- EG Score
- 3.0(low)
- EG Risk
- 30(Track)EG Risk 30/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 computedSeverity30% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
References (5)
- security-advisories@githubhttps://github.com/MobSF/Mobile-Security-Framework-MobSF/commit/62563ca429a75b3e5d47a13b958e1d2e7d5e2bbf
- security-advisories@githubhttps://github.com/MobSF/Mobile-Security-Framework-MobSF/pull/2627
- security-advisories@githubhttps://github.com/MobSF/Mobile-Security-Framework-MobSF/releases/tag/v4.5.1
- security-advisories@githubhttps://github.com/MobSF/Mobile-Security-Framework-MobSF/security/advisories/GHSA-95px-34x5-p37h
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/MobSF/Mobile-Security-Framework-MobSF/security/advisories/GHSA-95px-34x5-p37h
Vendor Advisories for CVE-2026-68927(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 7× in last 7d / 7× 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-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:24 UTCEG score recompute
- 2026-08-18 19:05 UTCEG score recompute
- 2026-08-18 18:22 UTCEG score recompute
- 2026-08-18 17:54 UTCEG score recompute
- 2026-08-18 17:54 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-68927?
CVE-2026-68927 is a low vulnerability published on August 18, 2026. MobSF is a mobile application security testing tool used. Prior to 4.5.1, getbrowsableactivities in mobsf/StaticAnalyzer/views/android/manifestanalysis.py validates only an Android manifest android:host value with validhost before appending a separately supplied android:port to the URL fetched by…
When was CVE-2026-68927 disclosed?
CVE-2026-68927 was first published in the National Vulnerability Database 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-68927 actively exploited?
CVE-2026-68927 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 81.8% of all scored CVEs.
What is the CVSS score of CVE-2026-68927?
CVE-2026-68927 has a CVSS v3 base score of 3.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-68927?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68927, 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-68927
Is Your Infrastructure Affected by CVE-2026-68927?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.