CVE-2025-31717: Android Unknown Package High Severity Vulnerability

:unknown: Updated 01 Dec 2025

Summary

01/12/2025
Yes i
High
Not published

CVE-2025-31717: ... 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 and devices. Android provides a rich application framework that allows developers to build innovative apps and games for mobile users. However, vulnerabilities in the Android ecosystem can lead to significant security risks, affecting millions of users and devices.

Vulnerability Detail

This vulnerability, identified as CVE-2025-31717, originates from a flaw in the Android package that allows unauthorized access or manipulation of sensitive data. The severity of this vulnerability is classified as high, indicating that it could be exploited by attackers to compromise user data or device integrity. The issue is present in versions prior to SoCVersion:2025-12-05, and it poses a significant risk to users who have not updated their systems.

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 the permissions of the affected application or avoid using it until the update is applied. This may help mitigate the risk of exploitation until a full patch is implemented.

Conclusion

In summary, CVE-2025-31717 is a high severity vulnerability in an Android package that poses significant risks to users. It is crucial to update to the patched version, SoCVersion:2025-12-05, to ensure device security. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2025-31717 is a high severity vulnerability in an unknown Android package that could allow unauthorized access to sensitive data.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor vulnerabilities without needing to sign up.

If you cannot update your device, consider limiting the permissions of the affected application or refrain from using it until a patch is available.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, potentially compromising user privacy and device security.

For more information on open-source vulnerabilities, you can visit Vulert at https://vulert.com, which provides real-time monitoring and alerts.

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