CVE-2026-82371

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Plaintext exposure of sensitive authentication data in Brocade SANnav discovery service log files enables individuals with file read access to retrieve administrative switch credentials and active session tokens. An attacker with access to system logs or support bundles can leverage exposed authentication details to compromise managed network infrastructure and access active application sessions. This vulnerability affects Brocade SANnav versions before 3.0.1a.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

October 1, 2026

Advisory Details (1)

Auto-updated Sep 24, 2026
No patch confirmed yet.
generic

Support Content Notification - Support Portal - Broadcom support portal

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38996

Vendor Advisories for CVE-2026-82371(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 13:12 UTCGHSA enrichment
  2. 2026-10-04 00:27 UTCEG score recompute
  3. 2026-10-04 00:27 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 11:43 UTCGHSA enrichment
  6. 2026-10-02 22:51 UTCEG score recompute
  7. 2026-10-02 22:51 UTCGHSA enrichment
  8. 2026-10-02 17:57 UTCEPSS rescore
  9. 2026-10-02 10:05 UTCGHSA enrichment
  10. 2026-10-01 21:21 UTCEG score recompute
  11. 2026-10-01 21:21 UTCGHSA enrichment
  12. 2026-10-01 20:38 UTCEG score recompute
  13. 2026-10-01 20:38 UTCGHSA enrichment
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 18:27 UTCGHSA enrichment
  16. 2026-10-01 05:42 UTCGHSA enrichment
  17. 2026-09-30 16:57 UTCEG score recompute
  18. 2026-09-30 16:57 UTCGHSA enrichment
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-30 04:12 UTCGHSA enrichment
  21. 2026-09-29 15:27 UTCEG score recompute
  22. 2026-09-29 15:27 UTCGHSA enrichment
  23. 2026-09-29 02:43 UTCEG score recompute
  24. 2026-09-29 02:43 UTCGHSA enrichment
  25. 2026-09-28 13:58 UTCEG score recompute
Show 18 more
  1. 2026-09-28 13:58 UTCGHSA enrichment
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 01:13 UTCEG score recompute
  4. 2026-09-28 01:13 UTCGHSA enrichment
  5. 2026-09-27 13:48 UTCEPSS rescore
  6. 2026-09-27 12:28 UTCGHSA enrichment
  7. 2026-09-26 23:43 UTCEG score recompute
  8. 2026-09-26 23:43 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 10:59 UTCEG score recompute
  11. 2026-09-26 10:59 UTCGHSA enrichment
  12. 2026-09-25 22:12 UTCGHSA enrichment
  13. 2026-09-25 09:22 UTCGHSA enrichment
  14. 2026-09-24 20:37 UTCEG score recompute
  15. 2026-09-24 19:38 UTCEG score recompute
  16. 2026-09-24 19:22 UTCEG score recompute
  17. 2026-09-24 18:27 UTCEG score recompute
  18. 2026-09-24 18:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82371?
CVE-2026-82371 is a high vulnerability published on September 24, 2026. Plaintext exposure of sensitive authentication data in Brocade SANnav discovery service log files enables individuals with file read access to retrieve administrative switch credentials and active session tokens. An attacker with access to system logs or support bundles can leverage exposed…
When was CVE-2026-82371 disclosed?
CVE-2026-82371 was first published on September 24, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82371 actively exploited?
CVE-2026-82371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82371?
CVE-2026-82371 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82371?
No fix for CVE-2026-82371 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-82371 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82371

Explore →

Is Your Infrastructure Affected by CVE-2026-82371?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs