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

CVE-2024-4610

CVE-2024-4610 is a Use After Free vulnerability in :unknown:. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2024-4610 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Also known asA-260126994
Published
Jul 1, 2024
Updated
Sep 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Sep 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • CISA’s SSVC triage classifies this CVE as under active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-4610.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.26%0.59%0.93%1.26%0.8%0.8%Mar 26Jul 26Sep 26

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

1 pkg affected
📦:unknown:

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦Android:unknown:SoCVersion:0&&< SoCVersion:2024-07-05SoCVersion:2024-07-05
Exploits & PoCs
2

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 :unknown:. 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.

  2. Fix

    Update :unknown: to SoCVersion:2024-07-05 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-4610 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-4610 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-2024-4610. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

CVE-2024-4610 is a security vulnerability affecting open source software. Review affected packages and apply the recommended fix as soon as possible.
O3 Security · Impact-Aware SCA

Is CVE-2024-4610 in your dependencies?

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

CVE-2024-4610: vulnerability details, affected… | O3 Security