Skip to content
major vulnerability· requires attention

Unauthenticated RCE in widely deployed FortiClient endpoints via DNS spoofing can lead to mass endpoint compromise across organizations.

Applications

CVE-2026-70465

8.1
High
EPSS 0.67%Patch availableAug 12, 2026

FortiClient Windows buffer overflow allows RCE via malicious DNS responses

common questions

Is CVE-2026-70465 being exploited?

Not confirmed. CVE-2026-70465 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.

How severe is CVE-2026-70465?

CVE-2026-70465 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-70465?

Yes. A fix has been recorded for CVE-2026-70465. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-70465 affect?

CVE-2026-70465 affects FortiClient Windows 7.4.0 - 7.4.3, FortiClient Windows 7.2.0 - 7.2.11. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70465?

Apply vendor patch when available; restrict/monitor DNS, use DNSSEC/validation, isolate affected endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
FortiClient Windows 7.4.0 - 7.4.3FortiClient Windows 7.2.0 - 7.2.11
impact

Unauthenticated remote code execution on Windows endpoints via crafted DNS replies, enabling full endpoint compromise and persistence.

action required

Immediate action required

affected versions
Fortinet FortiClientWindows
  • affected>= 7.4.0 and <= 7.4.3
  • affected>= 7.2.0 and <= 7.2.11

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free