CVE-2020-36376: An issue was discovered in the list function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary c

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2020-36376 is a critical-severity flaw (CVSS 9.8) affecting aaptjs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the list function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 21%)
CISA exploited list	No
Weakness	CWE-78
Published	2021-10-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: aaptjs project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-10-31 20:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

aaptjs project aaptjs DOWNGRADE

Affected: 1.3.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.3.1

1. Check installed version

apt-cache policy aaptjs || rpm -q aaptjs || aaptjs --version

2. No fixed release: DOWNGRADE to a release before 1.3.1 (Debian / Ubuntu)

apt-cache madison aaptjs sudo apt install aaptjs=<VERSION_BEFORE_1.3.1> sudo apt-mark hold aaptjs

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list aaptjs sudo dnf downgrade aaptjs-<VERSION_BEFORE_1.3.1> sudo dnf versionlock add aaptjs

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36376?

aaptjs: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-36376 being exploited?

CVE-2020-36376 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36376 affect?

CVE-2020-36376 affects aaptjs. Severity is critical (CVSS 9.8). An issue was discovered in the list function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.

How urgent is CVE-2020-36376?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2020-36381 CRITICAL 9.8 DOWNGRADE An issue was discovered in the singleCrunch function in shenzhim aaptjs 1.3.1, allows attackers to execute arb
CVE-2020-36380 CRITICAL 9.8 DOWNGRADE An issue was discovered in the crunch function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary
CVE-2020-36379 CRITICAL 9.8 DOWNGRADE An issue was discovered in the remove function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary
CVE-2020-36378 CRITICAL 9.8 DOWNGRADE An issue was discovered in the packageCmd function in shenzhim aaptjs 1.3.1, allows attackers to execute arbit
CVE-2020-36377 CRITICAL 9.8 DOWNGRADE An issue was discovered in the dump function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary c

References

← Back to latest CVEs