dbcve.org
Fabric Engine \(voss\)Operating system · Extremenetworks

CVE-2025-11192

HIGH · 8.6 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 9.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in Extreme Networks’ Fabric Engine (VOSS) before 9.3 was discovered. When SD-WAN AutoSense is enabled on a port, it may automatically configure fabric connectivity without validating ISIS authentication settings. The SD-WAN AutoSense implementation may be exploited by malicious actors by allowing unauthorized access to network fabric and configuration data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Extreme Networks Fabric Engine (VOSS) versions prior to 9.3, the SD-WAN AutoSense feature automatically configures fabric connectivity when enabled on a port without validating ISIS authentication settings. This allows malicious actors to gain unauthorized access to the network fabric and exfiltrate configuration data by exploiting the lack of authentication enforcement.

MitigationUpgrade VOSS to version 9.3 or later. Alternatively, disable SD-WAN AutoSense on affected ports until the upgrade can be performed, and ensure ISIS authentication is properly configured on all fabric-facing interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fabric Engine \(voss\)Operating system
Affected:< 9.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify VOSS version
    Use the command to display the software version installed on the Extreme Networks Fabric Engine device. Common commands include 'show software' or checking the boot prompt.
    Affected if The installed version is any release prior to 9.3 (for example, 9.2.x, 9.1.x, 8.x)
  2. Verify SD-WAN AutoSense status
    Locate the SD-WAN AutoSense configuration on the device. This is typically found in the port or interface configuration area. Use the appropriate show command such as 'show sdwan autosense' or 'show interface <port> sdwan' to see if the feature is enabled.
    Affected if SD-WAN AutoSense is enabled on any port or interface
  3. Review fabric-facing interfaces
    Identify all interfaces configured as fabric ports or participating in the fabric mesh. Use 'show fabric' or 'show mesh' related commands to list these interfaces.
    Affected if Any fabric-facing interfaces exist on the device
  4. Inspect ISIS authentication configuration
    On each fabric-facing interface identified, check the ISIS authentication settings. Use 'show isis interface' or similar command to display the authentication configuration for each interface.
    Affected if ISIS authentication is not configured, is disabled, or is set to 'none' on any fabric-facing interface

The environment is affected if the device runs VOSS version below 9.3 AND has SD-WAN AutoSense enabled on ports with fabric connectivity where ISIS authentication is missing or disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.3 or later
Fixed in 9.3
Interim mitigation

Upgrade VOSS to version 9.3 or later. Alternatively, disable SD-WAN AutoSense on affected ports until the upgrade can be performed, and ensure ISIS authentication is properly configured on all fabric-facing interfaces.

Recommended fix Moderate confidence

Fabric Engine v9.3

  1. Identify all Fabric Engine (VOSS) deployments running versions prior to 9.3 in the environment
  2. Inventory all ports where SD-WAN AutoSense is enabled using the CLI command 'show sdwan autosense port' or equivalent
  3. Schedule a maintenance window for the upgrade process
  4. Upgrade Fabric Engine to version 9.3 or later following the standard Extreme Networks upgrade procedure
  5. After upgrade, verify that SD-WAN AutoSense now properly validates ISIS authentication settings by checking fabric connectivity configuration
  6. Confirm that unauthorized fabric access is no longer possible by validating that authentication is enforced on AutoSense-enabled ports

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fabric Engine \(voss\) Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data