CVE-2024-47711

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-10-21. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-42630 (ENISA EUVD) · GHSA-ww56-mv6f-fwxf (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

af_unix: Don't return OOB skb in manage_oob().

syzbot reported use-after-free in unix_stream_recv_urg(). [0]

The scenario is

  • send(MSG_OOB)
  • recv(MSG_OOB)
-> The consumed OOB remains in recv queue
  • send(MSG_OOB)
  • recv()
-> manage_oob() returns the next skb of the consumed OOB -> This is also OOB, but unix_sk(sk)->oob_skb is not cleared
  • recv(MSG_OOB)
-> unix_sk(sk)->oob_skb is used but already freed

The recent commit 8594d9b85c07 ("af_unix: Don't call skb_get() for OOB skb.") uncovered the issue.

If the OOB skb is consumed and the next skb is peeked in manage_oob(), we still need to check if the skb is OOB.

Let's do so by falling back to the following checks in manage_oob() and add the test case in selftest.

Note that we need to add a similar check for SIOCATMARK.

[0]: BUG: KASAN: slab-use-after-free in unix_stream_read_actor+0xa6/0xb0 net/unix/af_unix.c:2959 Read of size 4 at addr ffff8880326abcc4 by task syz-executor178/5235

CPU: 0 UID: 0 PID: 5235 Comm: syz-executor178 Not tainted 6.11.0-rc5-syzkaller-00742-gfbdaffe41adc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call Trace: __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 unix_stream_read_actor+0xa6/0xb0 net/unix/af_unix.c:2959 unix_stream_recv_urg+0x1df/0x320 net/unix/af_unix.c:2640 unix_stream_read_generic+0x2456/0x2520 net/unix/af_unix.c:2778 unix_stream_recvmsg+0x22b/0x2c0 net/unix/af_unix.c:2996 sock_recvmsg_nosec net/socket.c:1046 [inline] sock_recvmsg+0x22f/0x280 net/socket.c:1068 ____sys_recvmsg+0x1db/0x470 net/socket.c:2816 ___sys_recvmsg net/socket.c:2858 [inline] __sys_recvmsg+0x2f0/0x3e0 net/socket.c:2888 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f5360d6b4e9 Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff29b3a458 EFLAGS: 00000246 ORIG_RAX: 000000000000002f RAX: ffffffffffffffda RBX: 00007fff29b3a638 RCX: 00007f5360d6b4e9 RDX: 0000000000002001 RSI: 0000000020000640 RDI: 0000000000000003 RBP: 00007f5360dde610 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007fff29b3a628 R14: 0000000000000001 R15: 0000000000000001

Allocated by task 5235: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:312 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:338 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3988 [inline] slab_alloc_node mm/slub.c:4037 [inline] kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4080 __alloc_skb+0x1c3/0x440 net/core/skbuff.c:667 alloc_skb include/linux/skbuff.h:1320 [inline] alloc_skb_with_frags+0xc3/0x770 net/core/skbuff.c:6528 sock_alloc_send_pskb+0x91a/0xa60 net/core/sock.c:2815 sock_alloc_send_skb include/net/sock.h:1778 [inline] queue_oob+0x108/0x680 net/unix/af_unix.c:2198 unix_stream_sendmsg+0xd24/0xf80 net/unix/af_unix.c:2351 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:745 ____sys_sendmsg+0x525/0x7d0 net/socket.c:2597 ___sys_sendmsg net/socket.c:2651 [inline] __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2680 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 5235: kasan_save_stack mm/kasan/common.c:47 ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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
10th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-27). 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

October 21, 2024

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
Patch available.
Web page

af_unix: Don't return OOB skb in manage_oob(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5aa57d9f2d5311f19434d95b2a81610aa263e23b
Web page

af_unix: Don't return OOB skb in manage_oob(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a7f9a2591a923bdde4bd7eac33490b6ae3b257c

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1022.23~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-27ubuntu
linuxKernel @ 6.11.2 (fixes >=6.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.2-1: fixed in 6.11.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.2-1: fixed in 6.11.2-1
—

Weakness Classification(1)

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

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 218 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 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-47711?
CVE-2024-47711 is a high-severity vulnerability; its CVE record was published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: af_unix: Don't return OOB skb in manage_oob(). syzbot reported use-after-free in unix_stream_recv_urg(). [0] The scenario is 1. send(MSG_OOB) 2. recv(MSG_OOB) -> The consumed OOB remains in recv queue 3. send(MSG_OOB) 4. recv() ->…
When was the CVE record for CVE-2024-47711 published?
The CVE record for CVE-2024-47711 was published on October 21, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-47711 actively exploited?
CVE-2024-47711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47711?
CVE-2024-47711 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-47711?
A fix for CVE-2024-47711 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-47711

Explore →

Is Your Infrastructure Affected by CVE-2024-47711?

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

Book a Demo →Browse All CVEs