mediumCVE-2026-59840

CVE-2026-59840 in FortiProxy

A buffer over-read vulnerability in Fortinet FortiOS 7.6.0 through 7.6.2, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2 all versions, FortiProxy 7.6.0 through 7.6.5, FortiProxy 7.4.0 through 7.4.13, FortiProxy 7.2 all versions may allow attacker to information...

ProductFortiProxy
CVSS4.3
EPSS0.00176
UpdatedJuly 15, 2026

Quick answer

Fortinet FortiProxy should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • FortiProxy 7.6.0 through 7.6.5
  • FortiProxy 7.4.0 through 7.4.13
  • FortiProxy 7.2 all versions

Fixed versions

  • FortiProxy 7.6.6 or later
  • FortiProxy 7.4.14 or later
  • Migrate FortiProxy 7.2 to a fixed release

How to fix it

Update FortiProxy. The old version can expose data, allow unsafe access, or let an attacker run commands.

  1. Check the exact Fortinet product and branch in use.
  2. Upgrade to FortiProxy 7.6.6 or later, FortiProxy 7.4.14 or later, Migrate FortiProxy 7.2 to a fixed release.
  3. Follow Fortinet upgrade path guidance.
  4. Limit admin access until the update is done.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the Fortinet product reports a fixed version.
  • Scan again and confirm CVE-2026-59840 is gone.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-59840?

Fortinet FortiProxy versions listed as affected should be reviewed: FortiProxy 7.6.0 through 7.6.5, FortiProxy 7.4.0 through 7.4.13, FortiProxy 7.2 all versions.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.