Skip to content
major vulnerability· requires attention

Unauthenticated access on a widely deployed network switch could enable credential exposure and log abuse across networks.

Networks

CVE-2025-59090

9.3
Critical
EPSS 1%Jan 26, 2026

Unauthenticated SOAP API on EXOS 9300 allows log manipulation and 2FA PIN access.

common questions

Is CVE-2025-59090 being exploited?

Not confirmed. CVE-2025-59090 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.

How severe is CVE-2025-59090?

CVE-2025-59090 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-59090?

Not known from our data. No patch reference has been recorded for CVE-2025-59090, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-59090 affect?

CVE-2025-59090 affects Extreme Networks EXOS 9300. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-59090?

Restrict API access; disable unauthenticated endpoints; patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Extreme Networks EXOS 9300
impact

Remote attacker can generate arbitrary logs and read 2FA PINs via unauthenticated SOAP API.

action required

Immediate action required

affected versions
dormakaba Kaba exos 9300
  • affected< 4.4.0
vendor says fixed in>= 4.4.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free