Skip to main content
VulnerabilityPublished Updated

CVE-2024-24995: Ivanti Avalanche · CWE-367

Affects Ivanti AvalancheSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 6.4.3 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.4.3
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Ivanti Avalanche to 6.4.3.

Affected software

ProductAffectedFixed in
Ivanti AvalancheAffected
  • =6.4.3
  • <6.4.3
Fixed in
  • 6.4.3

AI-suggested

  1. Immediately upgrade Ivanti Avalanche installations to version 6.4.3 or later, where the vulnerability is patched.
  2. Restrict access to the Ivanti Avalanche web interface to trusted administrators only, using network segmentation and firewall rules.
  3. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise.
  4. Regularly audit user accounts and permissions within Ivanti Avalanche to ensure the principle of least privilege is applied.
  5. Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected command executions or privilege escalations.
  6. Implement endpoint detection and response (EDR) solutions to detect and respond to suspicious behavior on managed devices.
  7. Conduct security awareness training for administrators to recognize phishing and social engineering attempts that could lead to credential theft.
  8. Develop and test incident response plans specific to endpoint management platform compromises.
  9. Stay informed about Ivanti security advisories and apply future patches promptly.
  10. Consider isolating critical management infrastructure from general network access to limit exposure.

Description

A Race Condition (TOCTOU) vulnerability in web component of Ivanti Avalanche before 6.4.3 allows a remote authenticated attacker to execute arbitrary commands as SYSTEM.

References

Community reviews

Loading reviews…