CVE-2025-61610: Android Package Vulnerability Leading to Denial of Service

:unknown: Updated 01 Dec 2025

Summary

01/12/2025
Yes i
High
Not published

CVE-2025-61610: ... 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 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 robust platform for app development, featuring a rich set of APIs and tools. However, like any software, it is susceptible to vulnerabilities that can compromise its functionality and security. This specific vulnerability can lead to a Denial of Service (DoS), impacting the availability of applications built on this platform.

Vulnerability Detail

This vulnerability originates from a flaw in the Android package that allows an attacker to exploit certain conditions, leading to a Denial of Service (DoS). The ramifications of this vulnerability can be severe, as it may render applications unresponsive or crash them entirely. The technical aspect of this vulnerability is tied to specific versions of the software, which can be targeted by malicious actors to disrupt services.

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 workaround, users can limit access to the affected components of the application or implement additional security measures to mitigate the risk of exploitation until the patch is applied.

Conclusion

In summary, CVE-2025-61610 is a significant vulnerability within the Android ecosystem that can lead to Denial of Service attacks. It is crucial for developers and users to update their packages to the patched version to ensure the security and availability of their applications. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2025-61610 is a vulnerability in the Android ecosystem that can lead to a Denial of Service (DoS) attack.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor for open-source vulnerabilities without requiring signup.

The consequences include potential application crashes and unavailability, which can disrupt user experience and service delivery.

Yes, a patch is available as of December 5, 2025. Users should update their packages to the latest version to mitigate the risk.

If you cannot apply the patch immediately, consider implementing temporary workarounds such as restricting access to vulnerable components.

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