CVE-2025-1976
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBrocade 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability in Brocade Fabric OS versions 9.1.0 through 9.1.1d6 allows a user with admin privileges to execute arbitrary code with full root privileges, bypassing the intended root access restrictions that were introduced in version 9.1.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.1.0, < 9.1.1d7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Fabric OS versionExecute the command to display the Fabric OS version, such as 'version' or 'firmwareShow' via admin CLI sessionAffected if The displayed version falls within the range 9.1.0 through 9.1.1d6 (i.e., version is >= 9.1.0 and < 9.1.1d7)
-
Confirm admin user accounts existList existing admin-level user accounts using 'userconfigshow' or equivalent admin CLI commandAffected if Any admin-level user accounts are present on the system, as these accounts can potentially exploit the privilege escalation
-
Verify root access statusAttempt to check current user privileges using 'whoami' or 'id' command via admin CLI, or review if root-level shell access is unexpectedly availableAffected if The system shows root-level privileges accessible to admin users, indicating the bypass of root access removal is present
-
Check firmware revision detailIf version shows 9.1.1, run 'firmwareShow' or 'version -detail' to confirm the exact build/revision (e.g., 9.1.1d6 or earlier)Affected if The specific build is 9.1.1d6 or earlier within the 9.1.x branch
The environment is affected if Fabric OS version is 9.1.0 through 9.1.1d6 and admin user accounts exist on the system, allowing authenticated admins to potentially escalate to full root privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.1.1d7
Upgrade Fabric OS to a version beyond 9.1.1d6 that includes the security fix for this privilege escalation vulnerability.
Fabric OS 9.1.1d7 or later
- Identify the current Fabric OS version by running 'firmwareShow' or checking the admin interface
- Download the fixed Fabric OS version 9.1.1d7 (or later) from the Broadcom Support Portal at support.broadcom.com
- Review upgrade prerequisites in the Fabric OS upgrade guide, including backup requirements
- Upload the firmware using 'firmwareUpload' or the web management interface
- Execute the firmware install using 'firmwareInstall' command or via the web interface
- Verify the upgrade was successful and the system is running version 9.1.1d7 or later using 'firmwareShow'
- Confirm the vulnerability is remediated by verifying the version is now >= 9.1.1d7
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1976 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1976 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data