Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 Android
CISA KEV · ACTIVELY EXPLOITED

CVE-2023-20963 — base

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. A fix is available for platform/frameworks/base — see the affected versions and patch details below.

Also known asA-220302519
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
6 known
Exploitation data as of Oct 23, 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 Risk0.00%
Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk
0.72%1.26%1.80%2.34%1.8%1.5%Apr 26Jul 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-220302519

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦Androidplatform/frameworks/base≥ 13-next:0&&< 13-next:2023-03-0113-next:2023-03-01
📦Androidplatform/frameworks/base≥ 11:0&&< 11:2023-03-0111:2023-03-01
📦Androidplatform/frameworks/base≥ 12:0&&< 12:2023-03-0112:2023-03-01
📦Androidplatform/frameworks/base≥ 12L:0&&< 12L:2023-03-0112L:2023-03-01
📦Androidplatform/frameworks/base≥ 13:0&&< 13:2023-03-0113:2023-03-01

Affected Products

1 product · 4 configurations
OS
androidgoogle
4 versions
11.012.012.113.0
Exploits & PoCs
6

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    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.

  3. Workarounds

    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.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-20963 in your dependencies?

Find it across Android, including transitive dependencies.

Actively Exploited: CVE-2023-20963: base