# CVE-2025-59407: Hardcoded credentials in n/a

> Hardcoded keystore password in Android app allows attackers to extract private keys, compromising security on Flock Safety devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2025
- **Updated:** 2 Oct 2025
- **Also known as:** GHSA-pv25-m64m-8qhp

## What is CVE-2025-59407?

CVE-2025-59407 is a critical vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-59407?

It affects 1 product.


Products: Flocksafety Flock Safety.

## How do I fix CVE-2025-59407?

No fix has been published for CVE-2025-59407 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59407 being exploited?

There is no known exploitation of CVE-2025-59407 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-59403](https://insights.sbomify.com/CVE-2025-59403/): Missing authorization in n/a (critical 9.8)
- [CVE-2025-59405](https://insights.sbomify.com/CVE-2025-59405/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2025-59406](https://insights.sbomify.com/CVE-2025-59406/): Hardcoded credentials in n/a (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59407 and fix it if it is affected.

What it is: CVE-2025-59407 is a critical vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59407 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59407/ (Markdown: https://insights.sbomify.com/CVE-2025-59407/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59407
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59407
- OSV: https://osv.dev/vulnerability/CVE-2025-59407

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59407/
Summaries are generated and may contain mistakes; the official description above is the record.