CVE-2025-61618: Android Unknown Package DoS Vulnerability

:unknown: Updated 01 Dec 2025

Summary

01/12/2025
Yes i
High
Not published

CVE-2025-61618: ... Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2025-12-05. Fixed in SoCVersion:2025-12-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 Your last release was probably never penetration tested 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 devices and applications. Android provides a rich application framework that allows developers to build innovative apps and games for mobile users. However, like any software, it can be susceptible to vulnerabilities that may compromise its functionality and security. This specific vulnerability poses a risk of Denial of Service (DoS), which can disrupt the normal operation of applications relying on this package.

Vulnerability Detail

This vulnerability, identified as CVE-2025-61618, originates from a flaw in the Android package that allows an attacker to exploit the system, leading to a Denial of Service (DoS) condition. The ramifications of this vulnerability can be severe, as it may render applications unresponsive or crash them entirely, affecting user experience and potentially leading to data loss. The vulnerability is classified as high severity, indicating that it poses a significant risk to users and applications relying on the affected package.

How To Fix

Minimum fixed version

SoCVersion:2025-12-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 a temporary measure, users can limit the use of the affected package until the patch is applied. This may involve disabling certain features or functionalities that rely on the vulnerable package, thereby reducing the risk of exploitation.

Conclusion

In summary, CVE-2025-61618 is a significant vulnerability affecting an unknown Android package, leading to potential Denial of Service conditions. Users are advised to update their packages to the patched version released on December 5, 2025, and consider temporary workarounds to mitigate risks until the update is applied.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

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

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The vulnerability can cause applications to become unresponsive or crash, leading to a poor user experience and potential data loss.

You can update your Android package by going to your device's settings and checking for system updates or downloading the latest version from the official Android repository.

Yes, a temporary workaround is to limit the use of the affected package until the patch is applied, which may involve disabling certain features.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2025-12-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