How severe is CVE-2023-20963?

No CVSS score has been assigned to CVE-2023-20963 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2023-20963?

CVE-2023-20963 affects the following packages: platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android). Ecosystems affected: Android.

How do I fix CVE-2023-20963?

Update platform/frameworks/base to 13-next:2023-03-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-20963 is resolved across your whole dependency graph.

How do I detect CVE-2023-20963 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base. 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-2023-20963 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-2023-20963?

O3 pinpoints whether CVE-2023-20963 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-2023-20963 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2023-20963, including 5 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-2023-20963?

CVE-2023-20963 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 72th 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-2023-20963 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-20963 (Android Framework Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-04-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-05-04. 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-2023-20963?

CVE-2023-20963 is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-20963 published, and has it been updated?

CVE-2023-20963 was published on March 1, 2023 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

CISA KEV · ACTIVELY EXPLOITED

CVE-2023-20963

CVE-2023-20963 is a CWE-295 vulnerability in platform/frameworks/base. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-04-13) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2023-20963 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Also known asA-220302519

Published

Mar 1, 2023

Updated

Sep 8, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

6 known

Exploitation data as of Aug 25, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-04-13. Federal agencies were required to remediate by 2023-05-04.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-20963.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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.

Real-World Exposure

5 pkgs affected

📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

Description

In WorkSource, there is a possible parcel mismatch. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`platform/frameworks/base`	≥ 13-next:0&&< 13-next:2023-03-01	13-next:2023-03-01
📦Android	`platform/frameworks/base`	≥ 11:0&&< 11:2023-03-01	11:2023-03-01
📦Android	`platform/frameworks/base`	≥ 12:0&&< 12:2023-03-01	12:2023-03-01
📦Android	`platform/frameworks/base`	≥ 12L:0&&< 12L:2023-03-01	12L:2023-03-01
📦Android	`platform/frameworks/base`	≥ 13:0&&< 13:2023-03-01	13:2023-03-01

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.