Quick answers
- Is CVE-2026-68923 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68923 being exploited in the wild.
- How severe is CVE-2026-68923?
- Medium severity, with a CVSS score of 6.5, published 18 August 2026.
- Which products and versions are affected?
- mobsf (PyPI) < 4.5.1, ECOSYSTEM:introduced=0,fixed=4.5.1.
- Is there a fix for CVE-2026-68923?
- Yes. mobsf (PyPI): upgrade to 4.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-68923 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-68923?
- Check whether you run mobsf (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mobsf (PyPI): upgrade to 4.5.1 or later
pip install "mobsf>=4.5.1"
Technical details
The vulnerability is a CSRF bypass caused by missing Django middleware configuration. The active MIDDLEWARE tuple in settings.py omits django.middleware.csrf.CsrfViewMiddleware, while an obsolete MIDDLEWARE_CLASSES setting (ignored by Django 2.0+) contains it. This leaves all POST endpoints (/delete_scan/, /upload/, /download_scan/, /change_password/, /create_user/, /delete_user/) unprotected. Exploitation requires a logged-in victim to visit an attacker-controlled page; the attacker embeds an HTML form that auto-submits to the target MobSF instance. Since session cookies are set with SameSite=Lax, the cookies are sent with top-level navigation, enabling the attack. No authentication is bypassed—the victim's existing session is abused. The fix is to add 'django.middleware.csrf.CsrfViewMiddleware' to the active MIDDLEWARE configuration. Version 4.5.1 and later include the remediation.
Affected products
- MobSF Mobile-Security-Framework-MobSF < 4.5.1
Identifiers
- CVE-2026-68923
- GHSA-3p54-567p-2wpr
- PYSEC-2026-3688
Timeline
- 2026-07-05: disclosed
- 2026-07-05: patched: Version 4.5.1 released with fix
- 2026-08-18: advisory: Published to GitHub Advisory Database