CVE-2026-0383
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 · uneditedA vulnerability in Brocade Fabric OS could allow an authenticated, local attacker with privileges to access the Bash shell to access insecurely stored file contents including the history command.
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 confidenceBrocade Fabric OS contains a vulnerability where an authenticated attacker with Bash shell privileges can access insecurely stored file contents, specifically including command history files. This exposes potentially sensitive commands and any credentials or configuration details that may have been entered via the CLI.
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.2.1c2>= 9.2.2, < 9.2.2b= 10.0.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 the Fabric OS versionRun 'version' or 'firmwareShow' command on the Fabric OS CLI to determine the installed version numberAffected if The version falls within < 9.2.1c2, >= 9.2.2 and < 9.2.2b, or equals 10.0.0
-
Verify Bash shell access on the deviceCheck which user accounts have Bash shell privileges by reviewing /etc/passwd or using 'userConfig -l' to list users and their shell assignmentsAffected if Any user account has Bash shell access enabled, not just the admin or root users intended for limited diagnostic use
-
Locate command history filesSearch for .bash_history, .sh_history, or similar history files in user home directories under /home/Affected if Command history files exist and contain sensitive commands or credentials that may have been entered via the CLI
You are affected if your Fabric OS version matches the vulnerable ranges AND any user has Bash shell access that could expose command history files.
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.2.1c29.2.2b
Apply the vendor patch from Brocade when available. In the interim, strictly limit who has Bash shell access on Fabric OS devices and consider rotating any credentials that may have been entered as commands.
9.2.1c2 (for 9.2.1.x branch), 9.2.2b (for 9.2.2.x branch), or 10.0.1 or later (for 10.0.x branch)
- Identify the current Fabric OS version using the `version` command or via the management interface
- Determine the appropriate upgrade path based on your current version branch
- If running version < 9.2.1c2, upgrade to version 9.2.1c2 or later in the 9.2.1.x branch
- If running version >= 9.2.2 and < 9.2.2b, upgrade to version 9.2.2b or later in the 9.2.2.x branch
- If running version 10.0.0, upgrade to version 10.0.1 or later
- Follow Broadcom's standard Fabric OS upgrade procedure documented at support.broadcom.com
- After upgrade, verify the version using `version` command and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0383 — 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-2026-0383 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