Skip to content
vulnerability

CVE-2024-55591

9.8
Critical
KEV · Exploited in wildEPSS 94%Patch available

An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] affecting FortiOS version 7.0.0 through 7.0.16 and FortiProxy version 7.0.0 through 7.0.19 and 7.2.0 through 7.2.12 allows a remote attacker to gain super-admin privileges via crafted requests to Node.js websocket module.

exploited
Yes, in CISA KEV since 14 Jan 2025fix by 21 Jan 2025 (CISA deadline for US federal agencies)known use in ransomware campaignsunvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 94.3%
Published 14 Jan 2025Analysed here 2 Nov 2026

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: partlyAV · networkCWE-288· Common Weakness

Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2024-55591 being exploited?

Yes. CVE-2024-55591 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-55591?

CVE-2024-55591 is rated Critical with a CVSS score of 9.8. 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-2024-55591?

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

What does CVE-2024-55591 affect?

CVE-2024-55591 affects fortinet:fortiproxy, fortinet:fortios. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

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

executive summary
technical analysis
affected
fortinet:fortiproxyfortinet:fortios
affected versions
Fortinet FortiOS
  • affected>= 7.0.0 and <= 7.0.16
Fortinet FortiProxy
  • affected>= 7.2.0 and <= 7.2.12
  • affected>= 7.0.0 and <= 7.0.19

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.

public exploits

Unvetted proof-of-concept code on GitHub: 10 GitHub proofs of concept · 1 Nuclei template

Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 22 Jan 2025 (SSVC 2.0.3).

timeline

  1. 14 Jan 2025Added to CISA KEV (exploited in the wild)
  2. 14 Jan 2025Published · 1 day later
  3. 16 Jan 2025First proof-of-concept repository on GitHub (unvetted) · 1 day later
  4. 21 Jan 2025CISA remediation due date (US federal agencies) · 5 days later
  5. 22 Jan 2025CISA SSVC assessment: exploitation active · 1 day later
  6. 5 Aug 2026CVE record last updated · 560 days (about 2 years) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 90 days (about 3 months) later
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
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 2 links

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved