Skip to main content
VulnerabilityPublished

CVE-2025-59407: Use of Hard-coded Cryptographic Key

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

Immediate mitigation should include the following steps: 1) Update or patch the Flock Safety DetectionProcessing application to a version that removes the hardcoded keystore and password, replacing it with a secure key management system that does not embed private keys in code. 2) If a patch is not yet available, restrict access to devices and application binaries to trusted personnel only and monitor for unauthorized access attempts. 3) Rotate any cryptographic keys associated with the compromised keystore to invalidate the exposed private key. 4) Implement network-level protections such as encryption and authentication for communications involving these devices to reduce the impact of key compromise. 5) Conduct audits of device firmware and application code to detect similar insecure key management practices. 6) Educate staff on the risks of hardcoded credentials and enforce secure coding practices for cryptographic material. 7) Monitor for suspicious activity that could indicate exploitation attempts, including anomalous device behavior or unexpected data access patterns.

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.

References

Community reviews

Loading reviews…