CVE-2026-23808 | Client Isolation Bypass via GTK Manipulation

A vulnerability has been identified in a standardized wireless roaming protocol that could enable a malicious actor to install an attacker-controlled Group Temporal Key (GTK) on a client device. Successful exploitation of this vulnerability could allow a remote malicious actor to perform unauthorized frame injection, bypass client isolation, interfere with cross-client traffic, and compromise network segmentation, integrity, and confidentiality.

Published: 2026-03-04 Last update: 2026-03-09 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-23808 is rated Low Risk (29.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.07%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-23808

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-05 0.03% 0.07% +0.05%
2 2026-03-05 0.03%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-23808

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 2.5 [email protected]
8.1 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 5.2 [email protected]

Weakness enumeration for CVE-2026-23808

Affected software / configurations for CVE-2026-23808

Vendor Product Version Raw CPE
arubanetworks arubaos >= 6.5.4.0, <= 8.10.0.21 cpe:2.3:o:arubanetworks:arubaos:*:*:*:*:*:*:*:*
arubanetworks arubaos >= 8.11.0.0, <= 8.12.0.6 cpe:2.3:o:arubanetworks:arubaos:*:*:*:*:*:*:*:*
arubanetworks arubaos >= 8.13.0.0, <= 8.13.1.1 cpe:2.3:o:arubanetworks:arubaos:*:*:*:*:*:*:*:*
arubanetworks arubaos >= 10.3.0.0, <= 10.4.1.10 cpe:2.3:o:arubanetworks:arubaos:*:*:*:*:*:*:*:*
arubanetworks arubaos >= 10.5.0.0, <= 10.7.2.2 cpe:2.3:o:arubanetworks:arubaos:*:*:*:*:*:*:*:*
arubanetworks arubaos 10.8.0.0 cpe:2.3:o:arubanetworks:arubaos:10.8.0.0:*:*:*:*:*:*:*

References for CVE-2026-23808

cvelogic Threat Intelligence