CVE-2024-50194

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-11-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-44696 (ENISA EUVD) · GHSA-8p49-gjw4-jcmp (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

arm64: probes: Fix uprobes for big-endian kernels

The arm64 uprobes code is broken for big-endian kernels as it doesn't convert the in-memory instruction encoding (which is always little-endian) into the kernel's native endianness before analyzing and simulating instructions. This may result in a few distinct problems:

* The kernel may may erroneously reject probing an instruction which can safely be probed.

* The kernel may erroneously erroneously permit stepping an instruction out-of-line when that instruction cannot be stepped out-of-line safely.

* The kernel may erroneously simulate instruction incorrectly dur to interpretting the byte-swapped encoding.

The endianness mismatch isn't caught by the compiler or sparse because:

* The arch_uprobe::{insn,ixol} fields are encoded as arrays of u8, so the compiler and sparse have no idea these contain a little-endian 32-bit value. The core uprobes code populates these with a memcpy() which similarly does not handle endianness.

* While the uprobe_opcode_t type is an alias for __le32, both arch_uprobe_analyze_insn() and arch_uprobe_skip_sstep() cast from u8[] to the similarly-named probe_opcode_t, which is an alias for u32. Hence there is no endianness conversion warning.

Fix this by changing the arch_uprobe::{insn,ixol} fields to __le32 and adding the appropriate __le32_to_cpu() conversions prior to consuming the instruction encoding. The core uprobes copies these fields as opaque ranges of bytes, and so is unaffected by this change.

At the same time, remove MAX_UINSN_BYTES and consistently use AARCH64_INSN_SIZE for clarity.

Tested with the following:

| #include | #include | | #define noinline __attribute__((noinline)) | | static noinline void *adrp_self(void) | { | void *addr; | | asm volatile( | " adrp %x0, adrp_self\n" | " add %x0, %x0, :lo12:adrp_self\n" | : "=r" (addr)); | } | | | int main(int argc, char *argv) | { | void *ptr = adrp_self(); | bool equal = (ptr == adrp_self); | | printf("adrp_self => %p\n" | "adrp_self() => %p\n" | "%s\n", | adrp_self, ptr, equal ? "EQUAL" : "NOT EQUAL"); | | return 0; | }

.... where the adrp_self() function was compiled to:

| 00000000004007e0 : | 4007e0: 90000000 adrp x0, 400000 <__ehdr_start> | 4007e4: 911f8000 add x0, x0, #0x7e0 | 4007e8: d65f03c0 ret

Before this patch, the ADRP is not recognized, and is assumed to be steppable, resulting in corruption of the result:

| # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0x4007e0 | EQUAL | # echo 'p /root/adrp-self:0x007e0' > /sys/kernel/tracing/uprobe_events | # echo 1 > /sys/kernel/tracing/events/uprobes/enable | # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0xffffffffff7e0 | NOT EQUAL

After this patch, the ADRP is correctly recognized and simulated:

| # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0x4007e0 | EQUAL | # | # echo 'p /root/adrp-self:0x007e0' > /sys/kernel/tracing/uprobe_events | # echo 1 > /sys/kernel/tracing/events/uprobes/enable | # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0x4007e0 | EQUAL

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.2%
EPSS %ILE
13th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 8, 2024

Last Modified

November 3, 2025

Vendor Advisories for CVE-2024-50194(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-10-24ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-10-24ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-24ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-10-24ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-24ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-24ubuntu
ubuntulinux-tools-gcp-lts-20.04 (5.4.0.1143.145) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1075.74) @ jammy2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.208.204) @ focal2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1058 (5.4.0-1058.62) @ focal2026-10-24ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1072.70) @ jammy2026-10-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-10-24ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1073.73) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1138.131) @ focal2026-10-24ubuntu
linuxKernel @ 4.19.323 (fixes >=4.10.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)
  • every version up to 6.1.115-1: fixed in 6.1.115-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.5-1: fixed in 6.11.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.5-1: fixed in 6.11.5-1
—

Additional Vendor Advisories

(24)

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 94 of 215 refreshes on record for this CVE.

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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-50194?
CVE-2024-50194 is a medium-severity vulnerability; its CVE record was published on November 8, 2024. In the Linux kernel, the following vulnerability has been resolved: arm64: probes: Fix uprobes for big-endian kernels The arm64 uprobes code is broken for big-endian kernels as it doesn't convert the in-memory instruction encoding (which is always little-endian) into the kernel's native endianness…
When was the CVE record for CVE-2024-50194 published?
The CVE record for CVE-2024-50194 was published on November 8, 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 3, 2025; the record at its source may have been updated since.
Is CVE-2024-50194 actively exploited?
CVE-2024-50194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50194?
CVE-2024-50194 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50194?
A fix for CVE-2024-50194 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50194 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-50194

Explore →

Is Your Infrastructure Affected by CVE-2024-50194?

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