Improper Neutralization of Argument Delimiters in a Decompiling Package Process in APKLeaks

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

EPSS

• CVE-2021-21386: 2.33% estimated exploitation activity in the next 30 days; percentile 83.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

APKLeaks prior to v2.0.4 allows remote authenticated attackers to execute arbitrary OS commands via package name inside the application manifest. Impact An authenticated attacker could include arguments that allow unintended commands or code to be executed, allow sensitive data to be read or modified, or could cause other unintended behavior through malicious package names. References - a966e781499ff6fd4eea66876d7532301b13a382 For more information If you have any questions or comments about this advisory: Email me at me@dw1.io

Published by the source

21 Jan 2022, 23:03 UTC

Last modified by the source

8 Jul 2026, 06:29 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8434-v7xw-8m9x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8434-v7xw-8m9x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-21386

Advisory: Improper Neutralization of Argument Delimiters in a Decompiling Package Process in APKLeaks
IDs: CVE-2021-21386, GHSA-8434-v7xw-8m9x
Record: https://patchnext.com/advisories/cve-2021-21386 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: apkleaks 2.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI apkleaks: affected < 2.0.4; fixed in 2.0.4

## Suggested inspection (read-only)
- `python -m pip show apkleaks`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apkleaks.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8434-v7xw-8m9x (OSV record GHSA-8434-v7xw-8m9x lists affected ranges: PyPI apkleaks >=0 <2.0.4 (fixed))
- Verified: https://github.com/advisories/GHSA-8434-v7xw-8m9x (GitHub-reviewed advisory GHSA-8434-v7xw-8m9x lists affected ranges: PyPI apkleaks >=0 <2.0.4)

Commands are suggestions: review each one before running it.