How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability none.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: None — an unauthenticated stranger can try it.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: None.
- Integrity impact: High — total loss, or loss the attacker controls.
- Availability impact: None.
Weakness class
CVE-2025-59404 is classified as CWE-1274: Improper Access Control for Volatile Memory Containing Boot Code. The product conducts a secure-boot process that transfers bootloader code from Non-Volatile Memory (NVM) into Volatile Memory (VM), but it does not have sufficient access control or other protections for the Volatile Memory.
Affected software
CVE-2025-59404 is recorded against 1 package.
- bravo-compute-box-firmware
Timeline and source
Published on 25 September 2025 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from NVD.
References
gainsec.com
gainsec.com
www.flocksafety.com
www.flocksafety.com
Other advisories for this package
bravo-compute-box-firmware has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-1274: Improper Access Control for Volatile Memory Containing Boot Code) in other software:
