CVE-2026-124599 · Other
NO FIX YET
An Android application package contains an RSA private key and public key, so anyone who extracts the app can read them. An attacker could use the key to impersonate the app, decrypt protected data, or perform unauthorized cryptographic operations.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any Android app that embeds an RSA private key in its package can have that key extracted by reverse engineering, so the risk sits with the app's developer rather than the phone user. The sources name no specific product or version, so teams should check their own Android apps for bundled private keys. Apps that keep keys in a server or hardware-backed keystore are not exposed by this flaw.
Not affected if hardware-keystore, keys-kept-server-side
Who cares android, mobile
BEGIN PRIVATE KEY or BEGIN RSA PRIVATE KEY.No fix yet, per the sources.
The RSA cryptographic key material, including a private key and public key, is embedded within the application package. Because Android applications can be extracted and reverse engineered, storing private cryptographic keys directly inside the client application may allow an attacker to recover the keys and potentially use them to impersonate the application, decrypt protected data, or generate unauthorized cryptographic operations.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.