BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-5047High confidence

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and authentication tokens in log files

Brocade · Brocade SANnav

8.2HighCVSS 4.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Brocade Brocade SANnav and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-94756

No EUVD known-exploited evidence

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.2 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.

What

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.

Why

The product stores sensitive information without properly limiting read or write access by unauthorized actors.

How

An attacker operating through an adjacent network may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.

Why

The product stores sensitive information without properly limiting read or write access by unauthorized actors.

How

An attacker operating through an adjacent network may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → Insecure Storage of Sensitive Information → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-922 ↗

CWE-922: Insecure Storage of Sensitive Information. The product stores sensitive information without properly limiting read or write access by unauthorized actors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
UnauthenticatedCWE-922
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-94756Official EUVD mapping

A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2562Broadcom Brocade SANnav: Mehrere Schwachstellen

Ein Angreifer aus einem angrenzenden Netzwerk kann mehrere Schwachstellen in Broadcom Brocade SANnav ausnutzen, um Informationen offenzulegen eine SQL Injektion durchzuführen und Daten zu manipulieren.

Official advisory ↗
CSIRT Italia · Italian · risolte-vulnerabilita-in-prodotti-brocadeRisolte vulnerabilità in prodotti Brocade

nuova finestra - - CVE-2026-87662 : apre una nuova finestra - - CVE-2026-87660 : apre una nuova finestra - - CVE-2026-87659 : apre una nuova finestra - - CVE-2026-87428 : apre una nuova finestra - - CVE-2026-87425 : apre una nuova finestra - - CVE-2026-87424 : apre una nuova finestra - - CVE-2026-85490 : apre una nuova finestra - - CVE-2026-85489 : apre una nuova finestra - - CVE-2026-85488 : apre una nuova finestra - - CVE-2026-85487 : apre una nuova finestra - - CVE-2026-85486 : apre una nuova finestra - - CVE-2026-85423 : apre una nuova finestra - - CVE-2026-85422 : apre una nuova finestra - - CVE-2026-85421 : apre una nuova finestra - - CVE-2026-5047 : apre una nuova finestra - - Riferimenti (37) https://support.broadcom.com/external/content/SecurityAdvisories/0/39078 https://support.broadcom.com/external/content/SecurityAdvisories/0/39149 https://support.broadcom.com/external/content/SecurityAdvisories/0/39077 https://support.broadcom.com/external/content/SecurityAdvisories/0/39076 https://support.broadcom.com/external/content/SecurityAdvisories/0/39135 https://support.broadcom.com/external/content/SecurityAdvisories/0/39137 https://support.broadcom.com/external/content/SecurityAdvisories/0/39164 https://support.broadcom.com/external/content/SecurityAdvisories/0/39145 https://support.br

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Brocade SANnav: 3.0.0, 0 < 2.4.0b
Fixed
Security update provided in Brocade SANnav 2.4.0b, 3.0.0 and 3.0.1
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 8 Oct 2026 · Last source change 8 Oct 2026, 17:55 UTC · CWE-922 · Insecure Storage of Sensitive Information

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-10-08
European sourceENISA EUVD · EUVD-2026-94756
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2026-94756 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-94756"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: support.broadcom.com/37933; removed remediation: wid.cert-bund.de/securityadvisory?name=WID-SEC-2026-2562.
    Before
    remediation: wid.cert-bund.de/securityadvisory?name=WID-SEC-2026-2562
    After
    remediation: support.broadcom.com/37933
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    Broadcom Brocade SANnav <3.0.0; Broadcom Brocade SANnav <2.4.0b; Broadcom Brocade SANnav <3.0.0a; Broadcom Brocade SANnav <3.0.1; Lenovo Computer · Fixed: No fixed version is explicitly recorded in this authority advisory.
    After
    Brocade SANnav: < 2.4.0b, 3.0.0 · Fixed: Security update provided in Brocade SANnav 2.4.0b, 3.0.0 and 3.0.1
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    CNA ↗
  5. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  6. CVSS scoreCVSS score changed from not recorded to 8.2 (CVSS 4.0 · CNA · CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N).
    Before
    not recorded
    After
    8.2 (CVSS 4.0 · CNA · CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N)
    CNA ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    Official national cybersecurity authority ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-94756↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-5047 · cve.blacktree.nl