CVE-2025-31931 is an uncontrolled search path vulnerability in the Intel Instrumentation and Tracing Technology API (ITT API) software before version 3.25.4 within Ring 3 user applications. The flaw arises from insecure search path handling, which can cause an application to load resources or code from an unintended location under attacker-influenced conditions. Intel indicates that exploitation by an unprivileged authenticated local adversary is possible in a high-complexity attack scenario and may result in escalation of privilege. The issue requires local access and active user interaction.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) Android application demonstrating exploitation of CVE-2025-31931, an arbitrary shared library loading vulnerability in the Intel ITT API as used in OpenCV 4.10+ on Android. The project is structured as a standard Android Studio project, with Java code for the app UI and C++ code for the native exploit payload. The main exploit logic resides in 'app/src/main/cpp/native-lib.cpp', which implements a shared library that, when loaded into a vulnerable process, determines the package name, notifies a remote Telegram bot via the Telegram API, and displays a Toast message on the device. The Java code in 'MainActivity.java' loads the native library and provides UI elements for user interaction. The exploit requires the attacker to load the malicious shared library into a vulnerable app process, which is possible due to the arbitrary library loading flaw. The repository includes build scripts, AndroidManifest, and resource files typical for an Android app. No hardcoded credentials are present; the Telegram bot token and chat ID must be supplied by the user. The exploit demonstrates both local notification (Toast) and remote notification (Telegram) capabilities, making it operational for vulnerability verification and demonstration.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.