# CVE-2026-22322: Stored Cross‑Site Scripting in Link Aggregation Name Handling

> An unauthenticated attacker can inject malicious scripts into switch configuration pages, allowing interface manipulation when viewed by administrators.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-j2wh-rp49-235f

## What is CVE-2026-22322?

CVE-2026-22322 is a high-severity cross-site scripting vulnerability in Phoenix Contact FL NAT 2008, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A stored cross‑site scripting (XSS) vulnerability in the Link Aggregation configuration interface allows an unauthenticated remote attacker to create a trunk entry containing malicious HTML/JavaScript code. When the affected page is viewed, the injected script executes in the context of the victim’s browser, enabling unauthorized actions such as interface manipulation. The session cookie is secured by the httpOnly Flag. Therefore an attacker is not able to take over the session of an authenticated user.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-22322 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22322 is a high-severity cross-site scripting vulnerability in Phoenix Contact FL NAT 2008, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22322 in the wild and no public exploit code.

Affected product: Phoenix Contact FL NAT 2008. 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-22322/ (Markdown: https://insights.sbomify.com/CVE-2026-22322/index.md)
```

## Sources

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

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