# CVE-2026-71407: Memory corruption in FortiOS

> Unauthenticated attackers can execute arbitrary code via crafted sockets if explicit proxy with Kerberos and SOCKS is enabled.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-32v4-7g7v-4c6p

## What is CVE-2026-71407?

CVE-2026-71407 is a medium-severity memory corruption vulnerability in Fortinet Fortios, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Stack-based Buffer Overflow vulnerability [CWE-121] vulnerability in Fortinet FortiOS 7.6.1 through 7.6.6 may allow an unauthenticated attacker who can bypass stack protection and ASLR to execute arbitrary code or commands in the context of the WAD daemon via crafted sockets, only if the explicit proxy is configured with Kerberos authentication and SOCKS enabled.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Fortinet Fortios.

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

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

## Is CVE-2026-71407 being exploited?

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

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71407 is a medium-severity memory corruption vulnerability in Fortinet Fortios, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71407 in the wild and no public exploit code.

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

## Sources

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

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