Authentication bypass via shared JWT signing key
Published Oct 8, 2026 · Updated Oct 8, 2026
Authentication bypass in Brocade ASCG before 3.5.0 allows attackers to access the SupportLink API using a shared cryptographic key. The API's JWT HMAC signing key is hardcoded across deployments, undermining authentication isolation between installations. Standard deployments are affected, and exploitation requires adjacent-network access and low privileges; specific unauthorized API operations are not disclosed.
Summary
What happened
Authentication bypass in Brocade ASCG before 3.5.0 allows attackers to access the SupportLink API using a shared cryptographic key. The API's JWT HMAC signing key is hardcoded across deployments, undermining authentication isolation between installations. Standard deployments are affected, and exploitation requires adjacent-network access and low privileges; specific unauthorized API operations are not disclosed.
The record
- CVE
- CVE-2026-87424
- Published
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Vendor
- Brocade Communications Systems
- Product
- Brocade Active Support Connectivity Gateway
- Classifications
- CWE-321, T1606
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 8, 2026CVE publishedPublication date reported by the CVE source.
- Oct 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started