CVE-2026-24077: Unknown Vulnerability in Android Ecosystem Package

:unknown: Updated 04 Jun 2026

Summary

01/06/2026
Yes i
Moderate
Not published

CVE-2026-24077: ... 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 part of the Android ecosystem, which is widely used for mobile applications. Android provides a rich application framework that allows developers to build innovative apps and games for mobile devices. This particular package is categorized as 'unknown', indicating that its specific functionality and attributes are not clearly defined. However, vulnerabilities in Android packages can lead to significant security risks, affecting user data and application integrity.

Vulnerability Detail

The vulnerability identified as CVE-2026-24077 originates from an unspecified issue within the Android ecosystem package. It has been classified with a moderate severity level, indicating that while it may not be critical, it still poses a risk to users and applications. The vulnerability could potentially allow unauthorized access or manipulation of data, leading to privacy breaches or application malfunctions. It is crucial for developers and users to be aware of such vulnerabilities to mitigate risks effectively.

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

Currently, no specific workarounds have been provided for this vulnerability. However, users are advised to monitor their applications closely and apply the patch as soon as it becomes available.

Conclusion

CVE-2026-24077 represents a moderate vulnerability in an unknown Android package that could lead to security risks for applications. Users are encouraged to update to the patched version once available and utilize tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2026-24077 is a moderate severity vulnerability affecting an unknown package within the Android ecosystem.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

The patch for this vulnerability is scheduled for release on June 5, 2026.

While waiting for the patch, it is advisable to monitor your application for any unusual behavior and prepare to apply the update as soon as it is available.

The risks include unauthorized access to data and potential manipulation of application functionality, which can compromise user privacy and security.

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