Authentication Bypass Vulnerability in the PAPI Protocol of AOS-8

published 2026-10-22 20d ago modified 2026-10-26 16d ago also EUVD-2026-108412

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits: 0; none known

An authentication bypass vulnerability in the PAPI protocol of AOS-8 could allow an unauthenticated remote attacker to circumvent existing authentication controls. Successful exploitation could allow an attacker to make limited unauthorized modifications to certain settings of the affected system.

Is CVE-2026-95718 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 19d ago (2026-10-23)

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

Hewlett Packard Enterprise (HPE) ArubaOS (AOS)

Classification

Weakness

CWE-287 Improper Authentication

References

support.hpe.com /hpesc/public/docDisplay?docId=hpesbnw05162en_us&docLocale=en_US

Sources

CVE List CVE-2026-95718
NVD CVE-2026-95718

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.