CVE-2026-20449: Android Unknown Package DoS Vulnerability

:unknown: Updated 04 Jun 2026

Summary

01/06/2026
Yes i
High
Not published

CVE-2026-20449: ... Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2026-06-05. Fixed in SoCVersion:2026-06-05. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The affected package is categorized under the Android ecosystem, which is widely used for mobile applications. Android provides a robust platform for developers to create applications that can run on a variety of devices. However, vulnerabilities can arise due to various factors, including improper handling of system resources. This specific vulnerability poses a risk of Denial of Service (DoS), potentially impacting the availability of applications relying on the affected package.

Vulnerability Detail

This vulnerability originates from a flaw in the Android system that allows an attacker to exploit certain conditions, leading to a Denial of Service (DoS). The severity of this vulnerability is classified as high, as it can disrupt the normal functioning of applications, making them unresponsive or unavailable. The vulnerability was introduced in SoCVersion:0 and is set to be fixed in SoCVersion:2026-06-05. It is crucial for developers to be aware of this issue to prevent potential exploitation.

How To Fix

Minimum fixed version

SoCVersion:2026-06-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As of now, no specific workarounds have been provided for this vulnerability. However, developers are encouraged to monitor their applications closely and apply the patch as soon as it becomes available.

Conclusion

In summary, CVE-2026-20449 is a significant vulnerability affecting an unknown Android package, leading to potential Denial of Service. It is crucial for developers to update to the patched version to mitigate risks and ensure application reliability. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2026-20449 is a high-severity vulnerability in an unknown Android package that can lead to Denial of Service (DoS).

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If your application is affected, you should update to the patched version available in SoCVersion:2026-06-05 as soon as possible.

The potential impacts include application unresponsiveness and service disruption, which can affect user experience and application reliability.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just the gradle.lockfile.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2026-06-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback