PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-5047 Brocade CVE debrief

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. This issue affects Brocade SANnav deployments, particularly those with access to log files, and requires defenders to assess exposure and prioritize securing log file access and reviewing current SANnav versions. The vulnerability class involves information disclosure through improper handling of sensitive data in logs.

Vendor
Brocade
Product
Brocade SANnav
CVSS
HIGH 8.2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-08
Original CVE updated
2026-10-08
Advisory published
2026-10-08
Advisory updated
2026-10-08

Who should care

Defenders responsible for Brocade SANnav deployments, particularly those with access to log files, should assess exposure and prioritize securing log file access and reviewing current SANnav versions.

Why it matters

CVE-2026-5047 vulnerability in Brocade SANnav requires defenders to assess exposure, prioritize log file security, and review current SANnav versions to mitigate potential authentication risks.

  • Potential unauthorized access to encoded passwords and authentication tokens
  • Increased risk of authentication compromise for SANnav users
  • Need for defenders to verify and secure log file access
  • Priority on reviewing current SANnav versions and assessing exposure

Technical summary

The vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and authentication tokens in log files, potentially allowing authenticated attackers with log file access to access passwords. This issue arises from improper handling of sensitive data in logs, affecting Brocade SANnav deployments. Defenders should prioritize verifying and securing log file access, reviewing current SANnav versions, and assessing exposure to potential authentication risks. The vulnerability does not involve remote code execution or elevation of privileges but requires defenders to assess and mitigate potential authentication risks.

Defensive priority

Defenders should prioritize verifying and securing log file access, reviewing current SANnav versions, and assessing exposure to potential authentication risks.

Recommended defensive actions

  • Verify and secure log file access for SANnav
  • Review current SANnav versions and assess exposure
  • Implement compensating controls for authentication risks
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability in Brocade SANnav, including affected versions and potential impacts. The vulnerability is confirmed in Brocade SANnav before 2.4.0b and 3.0.0. Defenders should verify log file access and review current SANnav versions. Evidence is limited to CVE and source item details; further verification is required.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-5047 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-5047

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-5047 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-5047

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • CVE-2026-5047

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/5xxx/CVE-2026-5047.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://support.broadcom.com/external/content/SecurityAdvisories/0/37933

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.