Threats / Broadcom / CVE-2025-1976
CVE-2025-1976
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Broadcom Brocade Fabric OS vulnerability
Broadcom Brocade Fabric OS contains a code injection vulnerability allowing local administrators to execute arbitrary code with root privileges.
Verdict
Today item — known-exploited.
A local code injection flaw in Brocade Fabric OS permits authenticated administrative users to achieve unauthenticated root code execution. Active exploitation in the wild indicates immediate operational risk to affected storage fabric infrastructure.
CISA KEV Yes · 2025-04-285EPSS 0.00694 (verify live)6CVSS 8.63CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-04-28).
Probability (EPSS)
EPSS 0.00694 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.6 (CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) · Affected: Broadcom, Brocade Fabric OS. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 4 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain initial access as a local user with administrative credentials through credential compromise or insider access.
Business
Administrative account compromise represents a critical control failure, enabling full infrastructure takeover without detection by standard perimeter controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I inject malicious code through the vulnerable input mechanism, bypassing input validation controls.
Business
Code injection execution at root level allows attackers to persist, exfiltrate data, or disrupt storage fabric operations affecting all dependent systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary commands with full root privileges on the Fabric OS system.
Business
Root-level compromise of storage fabric infrastructure can cascade to data theft, system destruction, or denial of service across enterprise storage networks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by brocadeCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.