CVE-2024-49369

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.9%, top 14% 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
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 9.8Exploit: NoneExposed: 0

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

Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. The TLS certificate validation in all Icinga 2 versions starting from 2.4.0 was flawed, allowing an attacker to impersonate both trusted cluster nodes as well as any API users that use TLS client certificates for authentication (ApiUser objects with the client_cn attribute set). This vulnerability has been fixed in v2.14.3, v2.13.10, v2.12.11, and v2.11.12.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track)
EG Risk 75/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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
85.6%
KEV
Not listed

Published

November 12, 2024

Last Modified

November 26, 2025

Advisory Details (8)

Auto-updated Jun 29, 2026
Patch available. Sources: github_commit, github.
generic Patch Available

[SECURITY] [DLA 3953-1] icinga2 security update

https://lists.debian.org/debian-lts-announce/2024/11/msg00010.html
generic

Critical Icinga 2 Security Update 2.14.3

https://icinga.com/blog/2024/11/12/critical-icinga-2-security-releases-2-14-3
github Patch Available

TLS Certificate Validation Bypass for JSON-RPC and HTTP API Connections · Advisory · Icinga/icinga2 · GitHub

https://github.com/Icinga/icinga2/security/advisories/GHSA-j7wq-r9mg-9wpv
github_commit Patch Available

commit 8fed6608912c (Icinga/icinga2)

Patch available: Icinga/icinga2 v2.11.12 (contains commit 8fed6608912c)

https://github.com/Icinga/icinga2/commit/8fed6608912c752b337d977f730547875a820831
github_commit

commit 869a7d6f0fe3 (Icinga/icinga2)

Fix landed in Icinga/icinga2 commit 869a7d6f0fe3 — awaiting tagged release

https://github.com/Icinga/icinga2/commit/869a7d6f0fe38c748e67bacc1fbdd42c933030f6
github_commit Patch Available

commit 3504fc7ed688 (Icinga/icinga2)

Patch available: Icinga/icinga2 v2.13.10 (contains commit 3504fc7ed688)

https://github.com/Icinga/icinga2/commit/3504fc7ed688c10d86988e2029a65efc311393fe
github_commit Patch Available

commit 2febc5e18ae0 (Icinga/icinga2)

Patch available: Icinga/icinga2 v2.14.3 (contains commit 2febc5e18ae0)

https://github.com/Icinga/icinga2/commit/2febc5e18ae0c93d989e64ebc2a9fd90e7205ad8
github_commit Patch Available

commit 0419a2c36de4 (Icinga/icinga2)

Patch available: Icinga/icinga2 v2.12.11 (contains commit 0419a2c36de4)

https://github.com/Icinga/icinga2/commit/0419a2c36de408e9a703aec0962061ec9a285d3c

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 42× 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-24 14:16 UTCEPSS rescore
  2. 2026-07-23 14:17 UTCEPSS rescore
  3. 2026-07-23 14:17 UTCEPSS rescore
  4. 2026-07-23 02:42 UTCEG score recompute
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-21 15:23 UTCEPSS rescore
  8. 2026-07-20 17:06 UTCEPSS rescore
  9. 2026-07-19 14:30 UTCEPSS rescore
  10. 2026-07-19 14:30 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-19 02:28 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-18 10:03 UTCEPSS rescore
  15. 2026-07-16 17:02 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:56 UTCEPSS rescore
  18. 2026-07-15 01:59 UTCEPSS rescore
  19. 2026-07-15 01:59 UTCEPSS rescore
  20. 2026-07-13 22:29 UTCEPSS rescore
  21. 2026-07-13 20:37 UTCOSV refresh
  22. 2026-07-13 06:12 UTCEPSS rescore
  23. 2026-07-12 05:45 UTCEPSS rescore
  24. 2026-07-12 05:45 UTCEPSS rescore
  25. 2026-07-11 08:26 UTCEPSS rescore
Show 64 more
  1. 2026-07-09 19:09 UTCEPSS rescore
  2. 2026-07-09 19:09 UTCEPSS rescore
  3. 2026-07-08 15:14 UTCEPSS rescore
  4. 2026-07-07 13:45 UTCEPSS rescore
  5. 2026-07-06 16:26 UTCEPSS rescore
  6. 2026-07-06 02:22 UTCEPSS rescore
  7. 2026-07-05 02:29 UTCEPSS rescore
  8. 2026-07-04 06:30 UTCEPSS rescore
  9. 2026-07-01 15:05 UTCEPSS rescore
  10. 2026-06-30 23:21 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 04:55 UTCEPSS rescore
  13. 2026-06-28 04:55 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-27 03:07 UTCEPSS rescore
  16. 2026-06-25 17:46 UTCOSV refresh
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-17 17:52 UTCEPSS rescore
  28. 2026-06-17 17:52 UTCEPSS rescore
  29. 2026-06-16 17:52 UTCEPSS rescore
  30. 2026-06-16 17:52 UTCEPSS rescore
  31. 2026-06-15 17:47 UTCEPSS rescore
  32. 2026-06-14 23:17 UTCEPSS rescore
  33. 2026-06-13 22:59 UTCEPSS rescore
  34. 2026-06-13 22:59 UTCEPSS rescore
  35. 2026-06-13 22:59 UTCEPSS rescore
  36. 2026-06-12 23:11 UTCEPSS rescore
  37. 2026-06-12 23:11 UTCEPSS rescore
  38. 2026-06-11 13:59 UTCEPSS rescore
  39. 2026-06-10 22:18 UTCEPSS rescore
  40. 2026-06-10 13:21 UTCEPSS rescore
  41. 2026-06-08 07:28 UTCOSV refresh
  42. 2026-06-06 13:46 UTCEPSS rescore
  43. 2026-06-06 13:46 UTCEPSS rescore
  44. 2026-06-05 22:46 UTCEPSS rescore
  45. 2026-06-05 22:46 UTCEPSS rescore
  46. 2026-06-04 13:11 UTCEPSS rescore
  47. 2026-06-04 13:11 UTCEPSS rescore
  48. 2026-06-02 20:12 UTCEPSS rescore
  49. 2026-06-01 13:51 UTCEPSS rescore
  50. 2026-06-01 13:51 UTCEPSS rescore
  51. 2026-05-31 00:16 UTCEPSS rescore
  52. 2026-05-31 00:16 UTCEPSS rescore
  53. 2026-05-29 13:43 UTCEPSS rescore
  54. 2026-05-28 13:44 UTCEPSS rescore
  55. 2026-05-28 13:44 UTCEPSS rescore
  56. 2026-05-28 13:44 UTCEPSS rescore
  57. 2026-05-27 13:40 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-26 13:43 UTCEPSS rescore
  60. 2026-05-26 13:43 UTCEPSS rescore
  61. 2026-05-26 07:18 UTCEPSS rescore
  62. 2026-05-26 07:18 UTCEPSS rescore
  63. 2026-05-26 07:18 UTCEPSS rescore
  64. 2026-05-23 18:33 UTCEG score recompute

Publicly available exploits

(1 reference)

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 PoCQuantum-Sicarius/CVE-2024-49369
    First seen Nov 29, 2024
    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-49369?
CVE-2024-49369 is a critical vulnerability published on November 12, 2024. Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. The TLS certificate validation in all Icinga 2 versions starting from 2.4.0 was flawed, allowing an attacker to impersonate both trusted cluster…
When was CVE-2024-49369 disclosed?
CVE-2024-49369 was first published in the National Vulnerability Database on November 12, 2024, with the most recent update on November 26, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-49369 actively exploited?
CVE-2024-49369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-49369?
CVE-2024-49369 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-49369?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-49369, 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-49369

Explore →

Is Your Infrastructure Affected by CVE-2024-49369?

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

Start Free Scan →Browse All CVEs