🛡️ CVE-2025-12600 — blu-ic2-firmware

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 high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

• 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: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2025-12600 is recorded against 2 packages.

• blu-ic2-firmware (fixed in 1.20)
• blu-ic4-firmware (fixed in 1.20)

Timeline and source

Published on 1 November 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

azure-access.com

Other advisories for this package

blu-ic2-firmware has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2025-12603 (9.8 Critical, published 1 Nov 2025)
• CVE-2025-12602 (9.8 Critical, published 1 Nov 2025)
• CVE-2025-12601 (7.5 High, published 1 Nov 2025)
• CVE-2025-12599 (9.8 Critical, published 1 Nov 2025)
• CVE-2025-12552 (9.8 Critical, published 31 Oct 2025)
• CVE-2025-12554 (9.8 Critical, published 31 Oct 2025)
• CVE-2025-12553 (9.8 Critical, published 31 Oct 2025)
• CVE-2025-12517 (5.3 Medium, published 30 Oct 2025)

Details

Affected Packages

References