How severe is CVE-2020-0041?

CVE-2020-0041 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-0041?

Affected package information for CVE-2020-0041 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-0041?

No patched version of the affected component has shipped for CVE-2020-0041 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2020-0041 in my code and dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2020-0041 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2020-0041?

O3 pinpoints whether CVE-2020-0041 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2020-0041 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2020-0041, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-0041?

CVE-2020-0041 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2020-0041 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-0041 (Android Kernel Out-of-Bounds Write Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2020-0041?

CVE-2020-0041 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-0041 published, and has it been updated?

CVE-2020-0041 was published on March 10, 2020 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2020-0041

HIGH

Published

Mar 10, 2020

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk87th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-145988638References: Upstream kernel

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In binder_transaction of binder.c, there is a possible out of bounds wri…

github.comGithubMar 2020

In binder_transaction of binder.c, there is a possible out of bounds wri…

github.comGithubAug 2020

In binder_transaction of binder.c, there is a possible out of bounds wri…

cisa.govCISAJul 2021

In binder_transaction of binder.c, there is a possible out of bounds wri…

github.comGithubAug 2023

Detection & mitigation playbook

Vulnerability

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of the affected component has shipped for CVE-2020-0041 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-0041 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-0041. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-0041 in your dependencies?

O3 detects CVE-2020-0041 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2020-0041

EPSS Exploitation Probability

Description

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2020-0041 in your dependencies?