# CVE-2026-119730: Maxthon Browser for Android < 7.5.8.103 Fullscreen Address Bar Spoofing


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-59rh-729h-3ffx

## What is CVE-2026-119730?

CVE-2026-119730 is a medium-severity vulnerability in Maxthon Browser for Android, published on 30 Oct 2026. 

### Official description

Maxthon Browser for Android before 7.5.8.103 contains an address bar spoofing vulnerability that allows remote attackers to misrepresent a page's origin by exploiting the lack of a persistent fullscreen notification or trusted origin indicator when the Fullscreen API is invoked. Attackers can craft a malicious web page that renders a counterfeit address bar showing a trusted domain while displaying attacker-controlled content, tricking users who perform a single tap to enter fullscreen into disclosing credentials via phishing.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information)

## Which versions are affected by CVE-2026-119730?


## How do I fix CVE-2026-119730?

No fix has been published for CVE-2026-119730 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119730 being exploited?

There is no known exploitation of CVE-2026-119730 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119730 and fix it if it is affected.

What it is: CVE-2026-119730 is a medium-severity vulnerability in Maxthon Browser for Android, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119730 in the wild and no public exploit code.

Affected product: Maxthon Browser for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119730/ (Markdown: https://insights.sbomify.com/CVE-2026-119730/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119730
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119730
- OSV: https://osv.dev/vulnerability/CVE-2026-119730

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119730/
Summaries are generated and may contain mistakes; the official description above is the record.