CVE-2020-0258

CVE-2020-0258 is a medium-severity vulnerability in Google Android with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-459.

Key facts

Description

In stopZygoteLocked of AppZygote.java, there is an insufficient cleanup. This could lead to local information disclosure in the application that is started next with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-157598956

Frequently asked questions

What is CVE-2020-0258?
In stopZygoteLocked of AppZygote.java, there is an insufficient cleanup. This could lead to local information disclosure in the application that is started next with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-157598956
How severe is CVE-2020-0258?
CVE-2020-0258 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-0258 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-0258?
CVE-2020-0258 affects Google Android. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-0258?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-0258 published?
CVE-2020-0258 was published on 2020-08-11 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Android

All CVEs affecting Google Android →

Other CWE-459 vulnerabilities

Browse all CWE-459 vulnerabilities →