How severe is CVE-2024-41955?

CVE-2024-41955 has a CVSS score of 5.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-41955?

CVE-2024-41955 affects the following packages: mobsf (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-41955?

Update mobsf to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41955 is resolved across your whole dependency graph.

How do I detect CVE-2024-41955 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mobsf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-41955 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2024-41955 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-41955, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-41955?

CVE-2024-41955 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-41955?

CVE-2024-41955 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2024-41955?

A Nuclei detection template exists for CVE-2024-41955, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-41955 published, and has it been updated?

CVE-2024-41955 was published on July 31, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2024-41955 — mobsf

MEDIUMFix: MobSF/Mobile-Security-Framework-MobSF@fdaad81

CVE-2024-41955 is a medium-severity (CVSS 5.2) Open Redirect vulnerability in mobsf. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for mobsf — see the affected versions and patch details below.

Mobile Security Framework (MobSF) has an Open Redirect in Login Redirect

Also known asGHSA-8m9j-2f32-2vx4PYSEC-2026-1669

Published

Jul 31, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-41955.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍mobsf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Who is impacted?

An open redirect vulnerability exist in MobSF authentication view.

PoC

Go to http://127.0.0.1:8000/login/?next=//afine.com in a web browser.
Enter credentials and press "Sign In".
You will be redirected to afine.com

Users who are not using authentication are not impacted.

Patches

Has the problem been patched? What versions should users upgrade to?

Update to MobSF v4.0.5

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? Disable Authentication

References

Are there any links users can visit to find out more? Fix: https://github.com/MobSF/Mobile-Security-Framework-MobSF/commit/fdaad81314f393d324c1ede79627e9d47986c8c8

Reporter

Marcin Węgłowski (AFINE Team)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mobsf`	all versions	4.0.5`pip install --upgrade 'mobsf==4.0.5'`

Affected Products

1 product · 1 configurations

Application

mobile security frameworkopensecurity

< 4.0.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Mobile Security Framework (MobSF) is a security research platform for mo…

github.comNVDAug 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mobsf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mobsf to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41955 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

How to detect CVE-2024-41955

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2024-41955 -u https://target

Template: Open Redirect in Login Redirect - MobSF
Severity: medium
Impact: An attacker can exploit this vulnerability to redirect users to malicious websites, leading to potential phishing attacks.
Remediation: Update Mobile Security Framework (MobSF) to the latest version that includes the fix from commit fdaad81.

Template by ProjectDiscovery nuclei-templates (Farish), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ An open redirect vulnerability exist in MobSF authentication view. PoC 1. Go to http://127.0.0.1:8000/login/?next=//afine.com in a web browser. 2. Enter credentials and press "Sign In". 3. You will be redirected to [afine.com](http://afine.com/) Users who are not using authentication are not impacted. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Update to MobSF v4.0.5 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Disable Authenticati