# CVE-2025-59408: Security feature bypass in n/a

> Attackers can flash modified firmware on Flock Safety Bravo devices because Secure Boot is disabled, enabling arbitrary code execution.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-7g8x-j62m-326m

## What is CVE-2025-59408?

CVE-2025-59408 is a high-severity vulnerability in n/a, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Flock Safety Bravo Edge AI Compute Device BRAVO_00.00_local_20241017 ships with Secure Boot disabled. This allows an attacker to flash modified firmware with no cryptographic protections.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Flocksafety Bravo Compute Box Firmware.

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

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

## Is CVE-2025-59408 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-59404](https://insights.sbomify.com/CVE-2025-59404/): Security feature bypass in n/a (high 7.5)
- [CVE-2025-59402](https://insights.sbomify.com/CVE-2025-59402/): Security feature bypass in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59408 is a high-severity vulnerability in n/a, published on 25 Sep 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-59408 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-59408/ (Markdown: https://insights.sbomify.com/CVE-2025-59408/index.md)
```

## Sources

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

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