CVE-2024-22024

HIGHNVD 8.39.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 95% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 8.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.3
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
CISA-KEV: Not listedEPSS: 95%CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An XML external entity or XXE vulnerability in the SAML component of Ivanti Connect Secure (9.x, 22.x), Ivanti Policy Secure (9.x, 22.x) and ZTA gateways which allows an attacker to access certain restricted resources without authentication.

CVSS v3
8.3
EG Score
9.0(high)
EG Risk
93(Attend)
EG Risk 93/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation95% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.8%
KEV
Not listed

Published

February 13, 2024

Last Modified

October 31, 2025

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:33 UTCEG score recompute
  2. 2026-07-22 23:20 UTCEG score recompute
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-15 16:56 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-07-07 13:45 UTCEPSS rescore
  8. 2026-07-06 16:26 UTCEPSS rescore
  9. 2026-07-06 02:22 UTCEPSS rescore
  10. 2026-07-06 02:22 UTCEPSS rescore
  11. 2026-06-28 14:06 UTCEPSS rescore
  12. 2026-06-28 14:06 UTCEPSS rescore
  13. 2026-06-28 04:55 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-24 14:04 UTCEPSS rescore
  17. 2026-06-23 21:32 UTCEPSS rescore
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-22 14:24 UTCEPSS rescore
  20. 2026-06-22 14:24 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-21 01:58 UTCEPSS rescore
  23. 2026-06-18 17:51 UTCEPSS rescore
  24. 2026-06-18 17:51 UTCEPSS rescore
  25. 2026-06-17 17:52 UTCEPSS rescore
Show 8 more
  1. 2026-06-17 17:52 UTCEPSS rescore
  2. 2026-06-15 17:47 UTCEPSS rescore
  3. 2026-05-31 22:30 UTCEPSS rescore
  4. 2026-05-31 22:30 UTCEPSS rescore
  5. 2026-05-26 07:18 UTCEPSS rescore
  6. 2026-05-26 07:18 UTCEPSS rescore
  7. 2026-05-24 08:44 UTCEG score recompute
  8. 2026-05-24 08:44 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0dteam/CVE-2024-22024
    First seen Feb 9, 2024

    Check for CVE-2024-22024 vulnerability in Ivanti Connect Secure

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-22024.yaml
    First seen Jan 1, 2024

    Ivanti Connect Secure - XXE

    Open source ↗

Frequently asked(5)

What is CVE-2024-22024?
CVE-2024-22024 is a high vulnerability published on February 13, 2024. An XML external entity or XXE vulnerability in the SAML component of Ivanti Connect Secure (9.x, 22.x), Ivanti Policy Secure (9.x, 22.x) and ZTA gateways which allows an attacker to access certain restricted resources without authentication.
When was CVE-2024-22024 disclosed?
CVE-2024-22024 was first published in the National Vulnerability Database on February 13, 2024, with the most recent update on October 31, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-22024 actively exploited?
CVE-2024-22024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-22024?
CVE-2024-22024 has a CVSS v3 base score of 8.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-22024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-22024, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-22024

Explore →

Is Your Infrastructure Affected by CVE-2024-22024?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.