{"answers":{"affected":"3 open source packages ship an affected version, including mobsf.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68924 exists.","fix":"Upgrade mobsf to 4.5.1 or later.","what":"CVE-2026-68924 is a medium-severity denial of service vulnerability in Mobile-Security-Framework-MobSF, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68924 and fix it if it is affected.\n\nWhat it is: CVE-2026-68924 is a medium-severity denial of service vulnerability in Mobile-Security-Framework-MobSF, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68924 exists.\n\nAffected packages and fixed versions:\n- mobsf (PyPI): affected all versions; fixed in 4.5.1\n- mobsf (PyPI): affected all versions; fixed in 4.5.1\n- mobsf (PyPI): affected all versions; fixed in 4.5.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68924/ (Markdown: https://insights.sbomify.com/CVE-2026-68924/index.md)","id":"CVE-2026-68924","markdown":"https://insights.sbomify.com/CVE-2026-68924/index.md","name":"CVE-2026-68924","record":{"aliases":["GHSA-x768-8642-mmq9","PYSEC-2026-3691"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MobSF security testing tool","requires_auth":"high_privilege","summary":"An authenticated user can cause disk exhaustion and service disruption in MobSF by uploading crafted archives that bypass per-file size limits.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"MobSF is a mobile application security testing tool used. Prior to 4.5.1, the unzip function in mobsf/StaticAnalyzer/views/common/shared_func.py logs that an archive member exceeding ZIP_MAX_UNCOMPRESSED_FILE_SIZE is being skipped but does not continue to the next member, so an authenticated user can upload a crafted ZIP or APK whose oversized member is extracted to disk when the aggregate ZIP_MAX_UNCOMPRESSED_TOTAL_SIZE limit has not yet been reached, potentially exhausting disk space and preventing further scans. This issue is fixed in version 4.5.1.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"MobSF: Zip Bomb Denial of Service via Per-File Size Limit Bypass in ZIP/APK Extraction","id":"CVE-2026-68924","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"MobSF: SSRF port restriction bypass in assetlinks_check","id":"CVE-2026-68927"},"packages":[{"ecosystem":"PyPI","fixed":["4.5.1"],"introduced":["0"],"last_affected":[],"package":"mobsf","purl":null,"source":"GHSA-x768-8642-mmq9"},{"ecosystem":"PyPI","fixed":["4.5.1"],"introduced":["0"],"last_affected":[],"package":"mobsf","purl":"pkg:pypi/mobsf","source":"GHSA-x768-8642-mmq9"},{"ecosystem":"PyPI","fixed":["4.5.1"],"introduced":["0"],"last_affected":[],"package":"mobsf","purl":"pkg:pypi/mobsf","source":"PYSEC-2026-3691"}],"prev":{"headline":"MobSF: CSRF checks not enforced after Django migration","id":"CVE-2026-68923"},"products":["Mobile-Security-Framework-MobSF"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["MobSF"]},"summary":"An authenticated user can cause disk exhaustion and service disruption in MobSF by uploading crafted archives that bypass per-file size limits.","url":"https://insights.sbomify.com/CVE-2026-68924/"}