CVE-2026-24413

MEDIUMNVD 5.55.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

Icinga 2 is an open source monitoring system. Starting in version 2.3.0 and prior to versions 2.13.14, 2.14.8, and 2.15.2, the Icinga 2 MSI did not set appropriate permissions for the %ProgramData%\icinga2\var folder on Windows. This resulted in the its contents - including the private key of the user and synced configuration - being readable by all local users. All installations on Windows are affected. Versions 2.13.14, 2.14.8, and 2.15.2 contains a fix. There are two possibilities to work around the issue without upgrading Icinga 2. Upgrade Icinga for Windows to at least version v1.13.4, v1.12.4, or v1.11.2. These version will automatically fix the ACLs for the Icinga 2 agent as well. Alternatively, manually update the ACL for the given folder C:\ProgramData\icinga2\var (and C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate to fix the issue for the Icinga for Windows as well) including every sub-folder and item to restrict access for general users, only allowing the Icinga service user and administrators access.

CVSS v3
5.5
EG Score
5.5(low)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

January 29, 2026

Last Modified

February 19, 2026

References (3)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 10× 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-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-24 14:17 UTCEPSS rescore
  4. 2026-07-23 03:07 UTCEG score recompute
  5. 2026-07-13 12:37 UTCOSV refresh
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 15:15 UTCEPSS rescore
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-25 07:31 UTCOSV refresh
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-23 21:32 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 17:53 UTCEPSS rescore
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-15 17:48 UTCEPSS rescore
  20. 2026-06-14 23:18 UTCEPSS rescore
  21. 2026-06-13 23:00 UTCEPSS rescore
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-10 22:18 UTCEPSS rescore
  24. 2026-06-10 22:18 UTCEPSS rescore
  25. 2026-06-08 14:17 UTCEPSS rescore
Show 21 more
  1. 2026-06-08 14:17 UTCEPSS rescore
  2. 2026-06-06 13:47 UTCEPSS rescore
  3. 2026-06-06 13:47 UTCEPSS rescore
  4. 2026-06-05 22:47 UTCEPSS rescore
  5. 2026-06-05 22:47 UTCEPSS rescore
  6. 2026-06-04 13:12 UTCEPSS rescore
  7. 2026-06-04 13:12 UTCEPSS rescore
  8. 2026-06-04 13:12 UTCEPSS rescore
  9. 2026-06-02 20:13 UTCEPSS rescore
  10. 2026-06-02 20:13 UTCEPSS rescore
  11. 2026-06-01 13:51 UTCEPSS rescore
  12. 2026-06-01 13:51 UTCEPSS rescore
  13. 2026-06-01 13:51 UTCEPSS rescore
  14. 2026-05-31 22:30 UTCEPSS rescore
  15. 2026-05-31 22:30 UTCEPSS rescore
  16. 2026-05-31 00:16 UTCEPSS rescore
  17. 2026-05-31 00:16 UTCEPSS rescore
  18. 2026-05-31 00:16 UTCEPSS rescore
  19. 2026-05-29 15:03 UTCEG score recompute
  20. 2026-05-29 13:44 UTCEPSS rescore
  21. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-24413?
CVE-2026-24413 is a medium vulnerability published on January 29, 2026. Icinga 2 is an open source monitoring system. Starting in version 2.3.0 and prior to versions 2.13.14, 2.14.8, and 2.15.2, the Icinga 2 MSI did not set appropriate permissions for the %ProgramData%\icinga2\var folder on Windows. This resulted in the its contents - including the private key of the…
When was CVE-2026-24413 disclosed?
CVE-2026-24413 was first published in the National Vulnerability Database on January 29, 2026, with the most recent update on February 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24413 actively exploited?
CVE-2026-24413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-24413?
CVE-2026-24413 has a CVSS v3 base score of 5.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-24413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24413, 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-2026-24413

Explore →

Is Your Infrastructure Affected by CVE-2026-24413?

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

Start Free Scan →Browse All CVEs