# CVE-2026-22627: Memory corruption in FortiSwitchAXFixed

> An unauthenticated attacker on the adjacent network can execute arbitrary code via a crafted LLDP packet due to a buffer overflow in FortiSwitchAXFixed.

- **Severity:** High 7.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **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:** 10 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-cj8g-r35p-7p2v

## What is CVE-2026-22627?

CVE-2026-22627 is a high-severity memory corruption vulnerability in Fortinet FortiSwitchAXFixed, published on 10 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A buffer copy without checking size of input ('classic buffer overflow') vulnerability in Fortinet FortiSwitchAXFixed 1.0.0 through 1.0.1 may allow an unauthenticated attacker within the same adjacent network to execute unauthorized code or commands on the device via sending a crafted LLDP packet.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Fortinet Fortiswitchaxfixed.

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

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

## Is CVE-2026-22627 being exploited?

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

## Other vulnerabilities in Fortinet FortiSwitchAXFixed

- [CVE-2026-22628](https://insights.sbomify.com/CVE-2026-22628/): Command injection in FortiSwitchAXFixed (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22627 is a high-severity memory corruption vulnerability in Fortinet FortiSwitchAXFixed, published on 10 Mar 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-22627 in the wild and no public exploit code.

Affected product: Fortinet FortiSwitchAXFixed. 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-22627/ (Markdown: https://insights.sbomify.com/CVE-2026-22627/index.md)
```

## Sources

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

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