VulnerabilityPublished 2 Oct 2025Updated 24 Nov 2025

CVE-2025-59403: Flock Safety Android Collins application · CVE-2025-59403 is a critical

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

9.8Critical

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

EPSS: 1.0% chance of exploitation in 30 days – higher than 64% 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:H/A:H

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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 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

Given the absence of available patches, European organizations should implement immediate compensating controls to mitigate CVE-2025-59403. First, restrict network access to port 8080 on affected devices by implementing strict firewall rules and network segmentation, ensuring only trusted management hosts can communicate with these endpoints. Disable or isolate wireless networks where these devices operate to reduce attacker access. Monitor network traffic for unusual connections to port 8080 or unexpected adb activity. Employ network intrusion detection systems (NIDS) with signatures for adb over TCP or suspicious API calls. Where possible, disable or restrict adb functionality on devices manually. Conduct thorough audits of device configurations and logs to detect any signs of compromise. Engage with Flock Safety support to obtain updates on patch availability and apply them promptly once released. Additionally, review physical security policies to ensure devices are deployed in secure environments minimizing unauthorized local network access. Educate IT and security teams about this vulnerability to enhance detection and response capabilities.

Description

CVE-2025-59403 is a critical vulnerability in the Flock Safety Android Collins application version 6.35.31, which manages camera feeds for Falcon, Sparrow, and Bravo devices. The app exposes administrative API endpoints on port 8080 without any authentication, including sensitive functions such as /reboot, /logs, /crashpack, and /adb/enable. This lack of authentication allows unauthenticated attackers on the same LAN/WLAN to perform denial of service by rebooting devices, access sensitive logs, and execute remote code by enabling adb over TCP without user confirmation. The remote code execution vector provides shell access, posing a severe risk to confidentiality, integrity, and availability. The vulnerability has a CVSS score of 9.8, indicating critical severity. European organizations using these devices are at risk, especially those relying on Flock Safety products for security monitoring. Immediate mitigation involves network segmentation, restricting access to port 8080, and monitoring for suspicious activity.

Impact

For European organizations, the impact of CVE-2025-59403 is significant due to the critical nature of the vulnerability and the role of affected devices in physical security infrastructure. Exploitation could lead to denial of service by rebooting security cameras, causing temporary loss of surveillance coverage. Information disclosure through access to logs could reveal sensitive operational details or network configurations, aiding further attacks. The most severe impact is remote code execution via enabling adb over TCP, which allows attackers to gain shell access and potentially pivot within the network, compromise other systems, or manipulate camera feeds and device configurations. This could undermine security monitoring, violate privacy regulations such as GDPR, and cause reputational damage. Organizations relying on Flock Safety devices for perimeter security, law enforcement, or critical infrastructure protection are particularly vulnerable. The vulnerability's exploitation requires network access, so organizations with poorly segmented or unsecured LAN/WLAN environments face higher risk. The absence of patches means that without immediate mitigations, European entities remain exposed to potential attacks that could disrupt security operations and lead to data breaches.

CWE-749Exposed Dangerous Method or Function (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
Architecture and Design
If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
Architecture and Design · Implementation · Attack Surface Reduction
Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users; restricted to a small set of privileged users; prevented from being directly accessible at all
OWASP Cheat Sheets
Third Party Javascript Management (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.1 (opens in a new tab)
V10.1.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
WebView Injection (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:42 UTC

WeaknessesCWE-749

Technical details

References

Community reviews

Related threats