CVE-2026-94584: Race Condition

Published Oct 8, 2026
·
Updated

A race condition and thread-safety vulnerability exists in the web management daemon of Brocade Fabric OS versions before 10.0.1. When handling user authentication requests across a multi-threaded execution pool, this race condition causes PAM modules to process stale or incorrect client IP addresses and switch context numbers. This leads to inaccurate audit records and potential access control bypasses where AAA evaluation or Calling-Station-ID ACL policies rely on client IP attributes.

Affected Software

1 affected component
Brocade Fabric OS<10.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Brocade Fabric OS to a version that resolves this vulnerability.

    Fixed in 10.0.1

Event History

Oct 8, 2026
CVE Published
via MITRE·03:14 AM
Data Sourced
via MITRE·03:14 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·04:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are most exposed to an access control impact?

Deployments whose AAA evaluation or Calling-Station-ID ACL policies depend on the client IP address are the ones identified as potentially subject to access control bypass. Environments that use those attributes only for logging are primarily exposed to inaccurate audit records.

2

What conditions are required for exploitation?

The issue occurs while the web management daemon handles user authentication requests across its multi-threaded execution pool. The supplied CVSS vector indicates adjacent-network attack access, high attack complexity, low privileges required, and no user interaction.

3

Are default configurations known to be affected?

The available information does not state whether the affected IP-dependent AAA or Calling-Station-ID ACL policies are enabled by default. The described access-control risk depends on configurations that rely on client IP attributes.

4

What can be done before upgrading?

The provided information does not specify a workaround. To reduce the described access-control risk, avoid relying on client IP attributes in AAA evaluation or Calling-Station-ID ACL policies until the device is updated.

5

How can administrators identify possible impact?

Review web-management authentication audit records for client IP addresses or switch context numbers that do not match the actual connecting client or expected context. Also identify AAA and Calling-Station-ID ACL policies that use client IP attributes, since those are the policies described as potentially bypassable.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203