CVE-2024-53197

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-04-09), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 4.1%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices

A bogus device can provide a bNumConfigurations value that exceeds the initial value used in usb_get_configuration for allocating dev->config.

This can lead to out-of-bounds accesses later, e.g. in usb_destroy_configuration.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100

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 (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (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, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
4.1%
EPSS %ILE
90th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

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

Exploitation active (CISA Vulnrichment) · Automatable no (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 & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (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

CISA required action“Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://lore.kernel.org/linux-cve-announce/2024122725-CVE-2024-53197-6aef@gregkh/ · https://source.android.com/docs/security/bulletin/2025-04-01 · https://nvd.nist.gov/vuln/detail/CVE-2024-53197

Published

December 27, 2024

Last Modified

November 4, 2025

Advisory Details (10)

Auto-updated Oct 12, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b909df18ce2a998afef81d58bbd1a05dc0788c40
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8f8b81dabe52b413fe9e062e8a852c48dd0680d
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b521b53ac6eb04e41c03f46f7fe452e4d8e9bcca
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b8460a2a7ce478e0b625af7c56d444dc24190f7
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9887d859cd60727432a01564e8f91302d361b72b
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/920a369a9f014f10ec282fd298d0666129379f1b
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62dc01c83fa71e10446ee4c31e0e3d5d1291e865
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/379d3b9799d9da953391e973b934764f01e03960
Web page

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b4ea4bfe16566b84645ded1403756a2dc4e0f19

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-10-13ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-10-13ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-10-13ubuntu
ubuntulinux-tools-fips (4.4.0.1115.116) @ xenial2026-10-13ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-10-13ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-13ubuntu
redhatopenshift/ose-rhel-coreos-8:412.86.202503310142-02025-04-10redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202503252048-02025-04-03redhat
redhatopenshift/ose-rhel-coreos-9:415.92.202503190057-02025-03-26redhat
redhatopenshift/ose-rhel-coreos-9:413.92.202503112237-02025-03-20redhat
redhatopenshift/ose-rhel-coreos-9:417.94.202503110101-02025-03-19redhat
redhatopenshift/ose-rhel-coreos-9:414.92.202503100617-02025-03-19redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202503102036-02025-03-18redhat
redhatkernel-0:4.18.0-193.146.1.el8_22025-03-11redhat
redhatkernel-0:5.14.0-503.31.1.el9_52025-03-11redhat
redhatkernel-0:5.14.0-284.108.1.el9_22025-03-10redhat
redhatkernel-0:2.6.32-754.56.1.el62025-03-10redhat
redhatkernel-0:5.14.0-427.59.1.el9_42025-03-10redhat
redhatkernel-rt-0:5.14.0-70.125.1.rt21.197.el9_02025-03-10redhat
redhatkernel-rt-0:5.14.0-284.108.1.rt14.393.el9_22025-03-10redhat
redhatkernel-rt-0:4.18.0-305.151.1.rt7.228.el8_42025-03-10redhat
redhatkernel-0:3.10.0-1160.133.1.el72025-03-10redhat
redhatkernel-0:4.18.0-305.151.1.el8_42025-03-10redhat
redhatkernel-rt-0:4.18.0-553.44.1.rt7.385.el8_102025-03-10redhat
redhatkernel-rt-0:3.10.0-1160.133.1.rt56.1285.el72025-03-10redhat
redhatkernel-0:3.10.0-1062.93.1.el72025-03-10redhat
redhatkernel-0:4.18.0-553.44.1.el8_102025-03-10redhat
redhatkernel-0:4.18.0-372.141.1.el8_62025-03-10redhat
redhatkernel-0:5.14.0-70.125.1.el9_02025-03-10redhat
redhatkernel-0:4.18.0-477.93.1.el8_82025-03-10redhat

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, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 59× in last 7d / 370× 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 100 of 1,788 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. None are among the latest 100 rows. The 1,688 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(6)

What is CVE-2024-53197?
CVE-2024-53197 is a critical-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices A bogus device can provide a bNumConfigurations value that exceeds the initial value used in usbgetconfiguration for allocating dev->config. This can…
When was the CVE record for CVE-2024-53197 published?
The CVE record for CVE-2024-53197 was published on December 27, 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 4, 2025; the record at its source may have been updated since.
Is CVE-2024-53197 actively exploited?
Yes. CISA added CVE-2024-53197 to the Known Exploited Vulnerabilities catalog on April 9, 2025, affecting Linux Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2024-53197?
CVE-2024-53197 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2024-53197?
CVE-2024-53197 affects Linux Kernel. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2024-53197?
A fix for CVE-2024-53197 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53197 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-53197

Explore →

Is Your Infrastructure Affected by CVE-2024-53197?

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