Skip to main content
← Vulnerabilities

In parseKnownActivityEmbeddingCerts of ParsingUtils.java, there is a possible permanent denial of service due to improper input validation.

Android is affected by a flaw in certificate parsing that can cause a permanent denial of service. Google's advisory rates it High. Fixed in Android 14, 15, 16, 16-qpr2, and 17.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 14, 15, 16, 16-qpr2, 17
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.

Published
Last modified
Published
Not listed in CISA KEV
0/100 · provisional
Unclear
Fix
Fixed in 14, 15, 16, 16-qpr2, 17
None on Exploit-DB, Metasploit or GitHub

Summary

In parseKnownActivityEmbeddingCerts of ParsingUtils.java, there is a possible permanent denial of service due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

What to do

  • Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Google Android

    17, 16-qpr2, 16, 15, 14

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-58817

What does this mean?

The flaw is in parseKnownActivityEmbeddingCerts in ParsingUtils.java. Improper input validation there can cause a permanent denial of service, meaning the affected component can stop working until it is fixed.Source: source.android.com

Am I affected, and how do I check?

The advisory names Google Android but does not list affected version ranges or setups. It lists fixed builds for Android 14, 15, 16, 16-qpr2, and 17, so compare your Android version against those branches and the advisory's security patch level.Source: source.android.com

What should I do about it?

Update to a fixed Android build on the 14, 15, 16, 16-qpr2, or 17 line. No workaround is listed in the facts.Source: source.android.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data