# CVE-2026-8480: Connection possible to the Administration portal with a revoked certificate

> Attackers with revoked certificates can bypass authentication to gain administrative access to the Stormshield Network Security portal.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-2j5q-9jw8-9qj5

## What is CVE-2026-8480?

CVE-2026-8480 is a medium-severity authentication bypass vulnerability in Stormshield Network Security, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was discovered on Stormshield Network Security 4.3.0  to 4.3.41 (included), 4.4.0 to 4.8.15 (included) , 5.0.2 EA to 5.0.5 (included)

A revoked client certificate can still be used to authenticate to the captive‑admin portal, allowing an attacker who possesses the revoked certificate to gain administrative access.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-8480?


## How do I fix CVE-2026-8480?

No fix has been published for CVE-2026-8480 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8480 being exploited?

There is no known exploitation of CVE-2026-8480 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8480 and fix it if it is affected.

What it is: CVE-2026-8480 is a medium-severity authentication bypass vulnerability in Stormshield Network Security, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8480 in the wild and no public exploit code.

Affected product: Stormshield Network Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8480/ (Markdown: https://insights.sbomify.com/CVE-2026-8480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8480
- OSV: https://osv.dev/vulnerability/CVE-2026-8480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8480/
Summaries are generated and may contain mistakes; the official description above is the record.