# CVE-2025-46335: Mobile Security Framework (MobSF) Allows Stored Cross Site Scripting (XSS) via malicious SVG Icon Upload

> Attackers can execute arbitrary scripts in MobSF by uploading malicious SVG icons during APK analysis, potentially compromising the security research platform.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 May 2025
- **Updated:** 5 May 2025
- **Also known as:** GHSA-mwfg-948f-2cc5, PYSEC-2026-1675

## What is CVE-2025-46335?

CVE-2025-46335 is a high-severity cross-site scripting vulnerability in Mobile-Security-Framework-MobSF, published on 5 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Mobile Security Framework (MobSF) is a security research platform for mobile applications in Android, iOS and Windows Mobile. A Stored Cross-Site Scripting (XSS) vulnerability has been identified in MobSF versions up to and including 4.3.2. The vulnerability arises from improper sanitization of user-supplied SVG files during the Android APK analysis workflow. Version 4.3.3 fixes the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-46335?

3 open source packages ship an affected version, including mobsf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mobsf` | PyPI | All versions | 4.3.3 |
| `mobsf` | PyPI | All versions | 4.3.3 |
| `mobsf` | PyPI | All versions | 4.3.3 |

Products: Opensecurity Mobile Security Framework.

## How do I fix CVE-2025-46335?

Upgrade mobsf to 4.3.3 or later.

## Is CVE-2025-46335 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46335 exists.

## Other vulnerabilities in Mobile-Security-Framework-MobSF

- [CVE-2025-24805](https://insights.sbomify.com/CVE-2025-24805/): Local Privilege Escalation in MobSF (high 8.5)
- [CVE-2025-24803](https://insights.sbomify.com/CVE-2025-24803/): Stored Cross-Site Scripting (XSS) in MobSF (high 8.4)
- [CVE-2026-24490](https://insights.sbomify.com/CVE-2026-24490/): MobSF has Stored XSS via Manifest Analysis - Dialer Code Host Field (high 8.1)
- [CVE-2024-53999](https://insights.sbomify.com/CVE-2024-53999/): Mobile Security Framework (MobSF) Stored Cross-Site Scripting Vulnerability in "Diff or Compare" Functionality (high 8.1)
- [CVE-2024-43399](https://insights.sbomify.com/CVE-2024-43399/): Mobile Security Framework (MobSF) has a Zip Slip Vulnerability in .a Static Library Files (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46335 and fix it if it is affected.

What it is: CVE-2025-46335 is a high-severity cross-site scripting vulnerability in Mobile-Security-Framework-MobSF, published on 5 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46335 exists.

Affected packages and fixed versions:
- mobsf (PyPI): affected all versions; fixed in 4.3.3
- mobsf (PyPI): affected all versions; fixed in 4.3.3
- mobsf (PyPI): affected all versions; fixed in 4.3.3

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-2025-46335/ (Markdown: https://insights.sbomify.com/CVE-2025-46335/index.md)
```

## Sources

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

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