Skip to content
major vulnerability· requires attention

Widely used Fortinet cloud management products; remote unauthenticated RCE risk could disrupt many orgs.

Cloud

CVE-2026-22828

8.1
High
EPSS 0.90%Patch availableApr 15, 2026

Heap-based buffer overflow in FortiAnalyzer Cloud and FortiManager Cloud; remote code execution.

common questions

Is CVE-2026-22828 being exploited?

Not confirmed. CVE-2026-22828 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.90% probability of exploitation in the next 30 days.

How severe is CVE-2026-22828?

CVE-2026-22828 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-22828?

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

What does CVE-2026-22828 affect?

CVE-2026-22828 affects FortiAnalyzer Cloud 7.6.2-7.6.4, FortiManager Cloud 7.6.2-7.6.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-22828?

Apply Fortinet patch when released; enable mitigations; monitor for probes.

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

executive summary
technical analysis
affected
FortiAnalyzer Cloud 7.6.2-7.6.4FortiManager Cloud 7.6.2-7.6.4
impact

Remote unauthenticated code execution via crafted requests; attacker could take control of FortiAnalyzer/FortiManager Cloud.

action required

Patch when possible

affected versions
Fortinet FortiAnalyzer Cloud
  • affected>= 7.6.2 and <= 7.6.4
Fortinet FortiManager Cloud
  • affected>= 7.6.2 and <= 7.6.4

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