CVE-2025-59407

Flocksafety Flock Safety hard-coded credentials

9.8 CRITICALPublic exploitEPSS 0.67%

Published2 Oct 2025

Description

The Flock Safety DetectionProcessing com.flocksafety.android.objects application 6.35.33 for Android (installed on Falcon and Sparrow License Plate Readers and Bravo Edge AI Compute Devices) bundles a Java Keystore (flock_rye.bks) along with its hardcoded password (flockhibiki17) in its code. The keystore contains a private key.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Flocksafety Flock Safety6.35.33

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://gainsec.com/2025/09/27/fly-by-device-2-the-falcon-sparrow-gated-wireless-rce-camera-feed-dos-information-disclosure-and-more/ExploitThird Party Advisory
https://gainsec.com/wp-content/uploads/2025/09/Root-from-the-Coop-Device-3_-Root-Shell-on-Flock-Safetys-Bravo-Compute-Box-GainSec.pdfExploitThird Party Advisory
https://www.flocksafety.com/productsProduct
https://www.flocksafety.com/products/license-plate-readersProduct

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-59407 being actively exploited?

CVE-2025-59407 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.67%.

How severe is CVE-2025-59407?

CVE-2025-59407 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.67% probability of exploitation.

Which products are affected by CVE-2025-59407?

Affected products include Flocksafety Flock Safety.

How do I fix CVE-2025-59407?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-59407 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.