ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-23811

A vulnerability in the client isolation mechanism may allow an attacker to bypass Layer 2 (L2) communication restrictions between clients and redirect traffic at Layer 3 (L3).

Published Mar 4, 2026 · catalog updated Jun 17, 2026 · A vulnerability in the

Check if you run it

No confirmed exploitation is on record for CVE-2026-23811. EPSS is 0.16%. Act only if a listed version of A vulnerability in the is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A vulnerability in the).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low3.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.16%
Remediation
Advisory link
Affected products
cpe arubanetworks/arubaos

A vulnerability in the client isolation mechanism may allow an attacker to bypass Layer 2 (L2) communication restrictions between clients and redirect traffic at Layer 3 (L3). In addition to bypassing policy enforcement, successful exploitation - when combined with a port-stealing attack - may enable a bi-directional Machine-in-the-Middle (MitM) attack.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe arubanetworks/arubaos10.8.0.0

How to fix CVE-2026-23811

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-23811. EPSS is 0.16%. Act only if a listed version of A vulnerability in the is installed.

Which versions are affected?

Compare what you have installed with 10.8.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-300. EPSS 0.16%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 4, 2026 · NIST NVD

    Detected

    A vulnerability in the client isolation mechanism may allow an attacker to bypass Layer 2 (L2) communication restrictions between clients and redirect traffic at Layer 3 (L3). In addition to bypassing policy enforcement, successful exploitation - when combined with a port-stealing attack - may enable a bi-directional Machine-in-the-Middle (MitM) attack.

  2. Jun 17, 2026 · NIST NVD

    Updated

    A vulnerability in the client isolation mechanism may allow an attacker to bypass Layer 2 (L2) communication restrictions between clients and redirect traffic at Layer 3 (L3). In addition to bypassing policy enforcement, successful exploitation - when combined with a port-stealing attack - may enable a bi-directional Machine-in-the-Middle (MitM) attack.

Sources

  • CVE.orgVulnerability recordCVE-2026-23811

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-23811

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-23811

    A vulnerability in the client isolation mechanism may allow an attacker to bypass Layer 2 (L2) communication restrictions between clients and redirect traffic at Layer 3 (L3). In addition to bypassing policy enforcement, successful exploitation - when combined with a port-stealin

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.