CVE-2025-52926VulnerabilityPublished 23 Jun 2025

CVE-2025-52926: spytrap-adb · Omission of Security-relevant Information

Affects spytrap-adbSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low : upgrade to 0.3.5 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.3.5

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade spytrap-org/spytrap-adb to 0.3.5.

Affected software

Product	Affected	Fixed in
GitHubspytrap-org/spytrap-adb`pkg:github/spytrap-org/spytrap-adb`Other threats	Affected <0.3.5	Fixed in 0.3.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations and users of spytrap-adb should: 1) Upgrade to spytrap-adb version 0.3.5 or later once it is released, as this version is expected to address the issue. 2) Until a patch is available, supplement spytrap-adb scans with alternative stalkerware detection tools that reliably report findings in their interfaces to avoid blind spots. 3) Implement strict access controls to limit local access to devices, reducing the risk of exploitation since local access is required. 4) Educate users about the importance of verifying scan results and encourage manual inspection of logs or scan outputs if accessible, to detect any anomalies not shown in the UI. 6) Consider integrating device monitoring solutions that provide comprehensive visibility into installed applications and processes, thereby compensating for any gaps in spytrap-adb's reporting.

Description

In scan.rs in spytrap-adb before 0.3.5, matches for known stalkerware are not rendered in the interactive user interface.

Impact

For European organizations, the impact of this vulnerability is relatively limited but non-negligible. Spytrap-adb is a specialized tool used to detect stalkerware, which is often employed in personal or corporate espionage contexts. The failure to display detected stalkerware could lead to undetected monitoring of employees or sensitive devices, potentially compromising privacy and internal security. While the vulnerability does not directly allow attackers to compromise systems or exfiltrate data, it undermines the reliability of a security tool, which could delay detection and response to stalkerware infections. This is particularly relevant for sectors handling sensitive personal data or intellectual property, such as finance, healthcare, and government agencies. However, since exploitation requires local access and user interaction, the risk of widespread automated attacks is low. The low CVSS score reflects the limited direct impact, but the indirect consequences of undetected stalkerware could be more significant in high-security environments.

CWE-223Omission of Security-relevant Information (opens in a new tab)
Base weaknessOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product does not record or display information that would be important for identifying the source or nature of an attack, or determining if an action is safe.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jun 2025, 01:05 UTC

WeaknessesCWE-223

Technical details

References

Community reviews