CVE-2024-49369

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.9% (87th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2024-43406 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.9%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.9%
EPSS %ILE
87th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 12, 2024

Last Modified

November 26, 2025

Advisory Details (8)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit, github.
Web pageMentions a patch (unverified)

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

https://lists.debian.org/debian-lts-announce/2024/11/msg00010.html
GitHub advisoryMentions a patch (unverified)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
icinga22.12.3-1
  • every version up to 2.12.3-1+deb11u1: fixed in 2.12.3-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
icinga22.13.6-2, 2.13.6-2+deb12u1
  • every version up to 2.13.6-2+deb12u2: fixed in 2.13.6-2+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
icinga2—
  • every version up to 2.14.3-1: fixed in 2.14.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
icinga2—
  • every version up to 2.14.3-1: fixed in 2.14.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 240 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:47 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  2. 2026-11-13 03:55 UTCEchelonGraph re-scored
  3. 2026-11-12 16:31 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  4. 2026-11-12 04:43 UTCEchelonGraph re-scored
  5. 2026-11-11 16:35 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  6. 2026-11-11 05:31 UTCEchelonGraph re-scored
  7. 2026-11-10 16:39 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  8. 2026-11-10 06:17 UTCEchelonGraph re-scored
  9. 2026-11-09 16:32 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  10. 2026-11-09 07:05 UTCEchelonGraph re-scored
  11. 2026-11-08 16:36 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  12. 2026-11-08 07:51 UTCEchelonGraph re-scored
  13. 2026-11-07 16:36 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  14. 2026-11-07 08:39 UTCEchelonGraph re-scored
  15. 2026-11-06 16:32 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  16. 2026-11-06 09:27 UTCEchelonGraph re-scored
  17. 2026-11-05 16:34 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  18. 2026-11-05 10:15 UTCEchelonGraph re-scored
  19. 2026-11-05 03:55 UTCOSV refresh
  20. 2026-11-04 16:32 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  21. 2026-11-04 10:58 UTCEchelonGraph re-scored
  22. 2026-11-03 16:43 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  23. 2026-11-03 11:46 UTCEchelonGraph re-scored
  24. 2026-11-02 12:33 UTCEchelonGraph re-scored
  25. 2026-11-01 13:20 UTCEchelonGraph re-scored
Show 72 more
  1. 2026-10-31 16:30 UTCEPSS rescoreEPSS 2.9% · 87th percentile
  2. 2026-10-31 14:08 UTCEchelonGraph re-scored
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  4. 2026-10-30 14:54 UTCEchelonGraph re-scored
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  6. 2026-10-29 15:42 UTCEchelonGraph re-scored
  7. 2026-10-28 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  8. 2026-10-27 17:07 UTCEchelonGraph re-scored
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  10. 2026-10-26 17:51 UTCEchelonGraph re-scored
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  12. 2026-10-25 16:59 UTCEchelonGraph re-scored
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  14. 2026-10-24 18:21 UTCEchelonGraph re-scored
  15. 2026-10-24 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  16. 2026-10-23 19:09 UTCEchelonGraph re-scored
  17. 2026-10-23 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  18. 2026-10-22 19:51 UTCEchelonGraph re-scored
  19. 2026-10-22 16:31 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  20. 2026-10-21 20:39 UTCEchelonGraph re-scored
  21. 2026-10-21 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  22. 2026-10-20 21:24 UTCEchelonGraph re-scored
  23. 2026-10-20 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  24. 2026-10-19 22:12 UTCEchelonGraph re-scored
  25. 2026-10-19 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  26. 2026-10-18 20:58 UTCEchelonGraph re-scored
  27. 2026-10-18 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  28. 2026-10-18 06:56 UTCEchelonGraph re-scored
  29. 2026-10-17 21:36 UTCEchelonGraph re-scored
  30. 2026-10-17 16:31 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  31. 2026-10-16 22:22 UTCEchelonGraph re-scored
  32. 2026-10-16 16:37 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  33. 2026-10-15 19:02 UTCEchelonGraph re-scored
  34. 2026-10-15 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  35. 2026-10-14 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  36. 2026-10-14 12:47 UTCEchelonGraph re-scored
  37. 2026-10-13 16:31 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  38. 2026-10-12 17:42 UTCEchelonGraph re-scored
  39. 2026-10-12 16:31 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  40. 2026-10-11 21:08 UTCEchelonGraph re-scored
  41. 2026-10-11 16:00 UTCEchelonGraph re-scored
  42. 2026-10-11 13:46 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  43. 2026-10-10 19:58 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  44. 2026-10-10 09:33 UTCOSV refresh
  45. 2026-10-09 20:05 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  46. 2026-10-08 17:08 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  47. 2026-10-07 23:46 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  48. 2026-10-06 15:16 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  49. 2026-10-05 17:41 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  50. 2026-10-03 14:24 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  51. 2026-10-01 22:41 UTCEchelonGraph re-scored
  52. 2026-10-01 19:48 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  53. 2026-09-30 15:02 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  54. 2026-09-29 15:18 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  55. 2026-09-27 13:44 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  56. 2026-09-26 15:57 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  57. 2026-09-24 14:01 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  58. 2026-09-23 13:46 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  59. 2026-09-22 14:47 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  60. 2026-09-20 20:14 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  61. 2026-09-20 18:44 UTCOSV refresh
  62. 2026-09-19 15:40 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  63. 2026-09-18 19:26 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  64. 2026-09-17 19:27 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  65. 2026-09-16 14:06 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  66. 2026-09-16 05:12 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  67. 2026-09-15 03:08 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  68. 2026-09-13 16:45 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  69. 2026-09-12 14:59 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  70. 2026-09-11 14:51 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  71. 2026-09-11 09:35 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  72. 2026-09-10 09:33 UTCEPSS rescoreEPSS 2.9% · 86th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCQuantum-Sicarius/CVE-2024-49369
    Published Nov 29, 2024
    Open source ↗

Frequently asked(5)

What is CVE-2024-49369?
CVE-2024-49369 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2024-49369 published?
The CVE record for CVE-2024-49369 was published on November 12, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 26, 2025; the record at its source may have been updated since.
Is CVE-2024-49369 actively exploited?
CVE-2024-49369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2024-49369 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.