CVE-2026-58500

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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 weekElevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

MCP Appium is an MCP server that provides AI assistants with tools to automate mobile app testing on Android and iOS. In versions prior to 1.85.10, the createLocatorGeneratorUI function interpolates attacker-controlled element attributes — text, content-desc, resource-id, and locator selector values — directly into an HTML template literal without any HTML or JavaScript context escaping. An attacker who controls the UI of the app under test can inject arbitrary HTML and JavaScript into the MCP UI resource returned by the generate_locators tool. When a victim's MCP client renders this resource, the injected script executes and can invoke arbitrary MCP tools via window.parent.postMessage, leading to unauthorized MCP tool execution such as taking screenshots, reading page source, or any other registered capability. This issue has been fixed in version 1.85.10.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
19.5%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github_commit Patch Available

commit e222bbbd6fe2 (appium/appium-mcp)

Patch available: appium/appium-mcp v1.85.10 (contains commit e222bbbd6fe2)

https://github.com/appium/appium-mcp/commit/e222bbbd6fe2b656a320efcd143563f08061a83d
github Patch Available🟡 PoC Available

Unescaped Locator Data XSS in MCP-UI Resource (createLocatorGeneratorUI) · Advisory · appium/appium-mcp · GitHub

https://github.com/appium/appium-mcp/security/advisories/GHSA-x975-rgx4-5fh4

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
appium-mcp—1.85.10—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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-16 01:05 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 12:11 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 23:15 UTCEG score recompute
  8. 2026-07-14 10:17 UTCEG score recompute
  9. 2026-07-13 21:23 UTCEG score recompute
  10. 2026-07-13 21:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58500?
CVE-2026-58500 is a high vulnerability published on July 13, 2026. MCP Appium is an MCP server that provides AI assistants with tools to automate mobile app testing on Android and iOS. In versions prior to 1.85.10, the createLocatorGeneratorUI function interpolates attacker-controlled element attributes — text, content-desc, resource-id, and locator selector…
When was CVE-2026-58500 disclosed?
CVE-2026-58500 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58500 actively exploited?
CVE-2026-58500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58500?
CVE-2026-58500 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-58500?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58500, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58500

Explore →

Is Your Infrastructure Affected by CVE-2026-58500?

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

Start Free Scan →Browse All CVEs