CVE-2026-0049
Persistent DoS via Resource Exhaustion in LocalImageResolver.java
Publication date: 2026-04-06
Last updated on: 2026-04-10
Assigner: Android (associated with Google Inc. or Open Handset Alliance)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| android | 14.0 | |
| android | 15.0 | |
| android | 16.0 | |
| android | 16.0 | |
| android | 16.0 | |
| android | 16.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-400 | The product does not properly control the allocation and maintenance of a limited resource. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2026-0049 is a security vulnerability in the Android Framework component, specifically in the onHeaderDecoded function of LocalImageResolver.java. It can cause a persistent local denial of service (DoS) due to resource exhaustion. Exploiting this vulnerability does not require any additional execution privileges or user interaction.
How can this vulnerability impact me? :
This vulnerability can lead to a local denial of service on affected Android devices, meaning the device or affected component could become unresponsive or crash due to resource exhaustion. No elevated privileges or user actions are needed to trigger this impact, which could disrupt normal device operation.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should apply the security patch included in the Android Security Bulletin for April 2026 or later, specifically security patch levels 2026-04-01 or newer.
Ensure that your Android devices are updated to versions 14, 15, 16, or 16-QPR2 with the latest security patches applied.
Avoid disabling platform and service mitigations that protect against this vulnerability unless absolutely necessary for development purposes.