VulnerabilityPublished 2 Oct 2025Updated 24 Nov 2025

CVE-2025-59405: Flock Safety Peripheral Android application used · CVE-2025-59405 is a high-severity

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 2 Oct 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

Organizations should immediately audit their deployments of the Flock Safety Peripheral Android application and related devices to identify affected versions. The primary mitigation is to remove any hardcoded API keys or secrets from client-side applications. Instead, secrets should be stored securely on backend servers or retrieved dynamically through secure authentication mechanisms. Implementing environment-based configuration and secret vaults (e.g., HashiCorp Vault, AWS Secrets Manager) is recommended. Additionally, rotate the exposed DataDog API keys immediately to invalidate compromised credentials. Monitor DataDog account activity for any unauthorized access or anomalies. Employ application hardening techniques such as code obfuscation and integrity checks to reduce the risk of reverse engineering. Finally, engage with the vendor for official patches or updates that address this vulnerability and apply them promptly once available. Network segmentation and strict access controls around monitoring infrastructure can further limit the impact of potential exploitation.

Description

CVE-2025-59405 is a high-severity vulnerability in the Flock Safety Peripheral Android application used on license plate readers and AI compute devices. The app contains a cleartext DataDog API key embedded in its codebase, which can be trivially extracted by decompiling the application binaries without any privileges or user interaction. This exposure allows attackers to access the DataDog monitoring service with the compromised OAuth secret, potentially leading to unauthorized data access or manipulation. Although no known exploits are currently reported in the wild, the vulnerability poses a significant confidentiality risk. European organizations using these devices could face data leakage or monitoring disruption. Mitigation requires removing the embedded secret from client-side code and implementing secure secret management practices. Countries with higher adoption of smart city and law enforcement technologies, such as Germany, France, and the UK, are more likely to be affected. The vulnerability has a CVSS score of 7.5, reflecting its high impact on confidentiality with no required privileges or user interaction.

Impact

For European organizations, especially those involved in law enforcement, smart city infrastructure, or traffic monitoring, this vulnerability could lead to unauthorized access to sensitive monitoring data collected by license plate readers and AI compute devices. Attackers leveraging the exposed DataDog API key could access logs, telemetry, or configuration data, potentially gaining insights into surveillance operations or disrupting monitoring capabilities. This could result in confidentiality breaches, loss of trust, and operational challenges. Additionally, if attackers manipulate monitoring data or configurations, it could impair incident detection and response. The impact is particularly significant for public safety agencies and municipalities relying on these devices for security and traffic management. Furthermore, the exposure of such secrets could facilitate further attacks or lateral movement within networks if combined with other vulnerabilities. The absence of known exploits currently provides a window for mitigation, but the ease of key extraction means the threat could materialize rapidly once discovered by malicious actors.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (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

Description

AI analysisMachine-generated, updated 1 Dec 2025, 14:43 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats