How severe is CVE-2025-1976?

No CVSS score has been assigned to CVE-2025-1976 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-1976?

Affected package information for CVE-2025-1976 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-1976?

No fixed release is recorded for CVE-2025-1976 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2025-1976 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2025-1976 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2025-1976 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-1976 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-1976?

CVE-2025-1976 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-1976 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-1976 (Broadcom Brocade Fabric OS Code Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-04-28. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-05-19. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-1976?

CVE-2025-1976 is classified as Code Injection (CWE-94), OS Command Injection (CWE-78). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-1976 published, and has it been updated?

CVE-2025-1976 was published on April 24, 2025 and was last updated on February 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2025-1976

CVE-2025-1976 is a Code Injection vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-04-28) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Brocade Fabric OS versions starting with 9.1.0 have root access removed, however, a local user with admin privilege can potentially execute arbitrary code with full root privileges…

Published

Apr 24, 2025

Updated

Feb 26, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-04-28. Federal agencies were required to remediate by 2025-05-19.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-1976.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Brocade Fabric OS versions starting with 9.1.0 have root access removed, however, a local user with admin privilege can potentially execute arbitrary code with full root privileges on Fabric OS versions 9.1.0 through 9.1.1d6.

Affected Products

1 product · 1 configurations

fabric operating systembroadcom

≥ 9.1.0 && < 9.1.1d7

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2025-1976 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-1976 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works