Skip to main content
VulnerabilityPublished Updated

CVE-2024-24482: Apktool · Path Traversal

Affects ApktoolSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.9.3 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.9.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade ibotpeaches/Apktool to 2.9.3.

Affected software

ProductAffectedFixed in
GitHubibotpeaches/Apktoolpkg:github/ibotpeaches/ApktoolOther threatsAffected
  • <2.9.3
Fixed in
  • 2.9.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-24482, organizations should immediately restrict network access to systems running vulnerable versions of Aprktool, especially from untrusted networks. Employ strict input validation and sanitization on any interfaces interacting with Aprktool to detect and block directory traversal sequences such as '../' or '/..'. Monitor logs and network traffic for unusual file access patterns or directory traversal attempts. Implement application-layer firewalls or intrusion prevention systems with rules targeting directory traversal signatures. As an interim measure, consider running Aprktool with least privilege, limiting its file system permissions to only necessary directories to reduce potential damage. Conduct security awareness training for developers and administrators about the risks of directory traversal vulnerabilities and secure coding practices. Finally, maintain regular backups and incident response plans to quickly recover from any potential exploitation.

Description

Aprktool before 2.9.3 on Windows allows ../ and /.. directory traversal.

References

Community reviews

Loading reviews…