CVE-2024-26792

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-04-04. 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-24054 (ENISA EUVD) · GHSA-7w6v-jhvx-qx5c (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:

btrfs: fix double free of anonymous device after snapshot creation failure

When creating a snapshot we may do a double free of an anonymous device in case there's an error committing the transaction. The second free may result in freeing an anonymous device number that was allocated by some other subsystem in the kernel or another btrfs filesystem.

The steps that lead to this:

1) At ioctl.c:create_snapshot() we allocate an anonymous device number and assign it to pending_snapshot->anon_dev;

2) Then we call btrfs_commit_transaction() and end up at transaction.c:create_pending_snapshot();

3) There we call btrfs_get_new_fs_root() and pass it the anonymous device number stored in pending_snapshot->anon_dev;

4) btrfs_get_new_fs_root() frees that anonymous device number because btrfs_lookup_fs_root() returned a root - someone else did a lookup of the new root already, which could some task doing backref walking;

5) After that some error happens in the transaction commit path, and at ioctl.c:create_snapshot() we jump to the 'fail' label, and after that we free again the same anonymous device number, which in the meanwhile may have been reallocated somewhere else, because pending_snapshot->anon_dev still has the same value as in step 1.

Recently syzbot ran into this and reported the following trace:

------------[ cut here ]------------ ida_free called for id=51 which is not allocated. WARNING: CPU: 1 PID: 31038 at lib/idr.c:525 ida_free+0x370/0x420 lib/idr.c:525 Modules linked in: CPU: 1 PID: 31038 Comm: syz-executor.2 Not tainted 6.8.0-rc4-syzkaller-00410-gc02197fc9076 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 RIP: 0010:ida_free+0x370/0x420 lib/idr.c:525 Code: 10 42 80 3c 28 (...) RSP: 0018:ffffc90015a67300 EFLAGS: 00010246 RAX: be5130472f5dd000 RBX: 0000000000000033 RCX: 0000000000040000 RDX: ffffc90009a7a000 RSI: 000000000003ffff RDI: 0000000000040000 RBP: ffffc90015a673f0 R08: ffffffff81577992 R09: 1ffff92002b4cdb4 R10: dffffc0000000000 R11: fffff52002b4cdb5 R12: 0000000000000246 R13: dffffc0000000000 R14: ffffffff8e256b80 R15: 0000000000000246 FS: 00007fca3f4b46c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f167a17b978 CR3: 000000001ed26000 CR4: 0000000000350ef0 Call Trace: btrfs_get_root_ref+0xa48/0xaf0 fs/btrfs/disk-io.c:1346 create_pending_snapshot+0xff2/0x2bc0 fs/btrfs/transaction.c:1837 create_pending_snapshots+0x195/0x1d0 fs/btrfs/transaction.c:1931 btrfs_commit_transaction+0xf1c/0x3740 fs/btrfs/transaction.c:2404 create_snapshot+0x507/0x880 fs/btrfs/ioctl.c:848 btrfs_mksubvol+0x5d0/0x750 fs/btrfs/ioctl.c:998 btrfs_mksnapshot+0xb5/0xf0 fs/btrfs/ioctl.c:1044 __btrfs_ioctl_snap_create+0x387/0x4b0 fs/btrfs/ioctl.c:1306 btrfs_ioctl_snap_create_v2+0x1ca/0x400 fs/btrfs/ioctl.c:1393 btrfs_ioctl+0xa74/0xd40 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:871 [inline] __se_sys_ioctl+0xfe/0x170 fs/ioctl.c:857 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x6f/0x77 RIP: 0033:0x7fca3e67dda9 Code: 28 00 00 00 (...) RSP: 002b:00007fca3f4b40c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fca3e7abf80 RCX: 00007fca3e67dda9 RDX: 00000000200005c0 RSI: 0000000050009417 RDI: 0000000000000003 RBP: 00007fca3e6ca47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fca3e7abf80 R15: 00007fff6bf95658

Where we get an explicit message where we attempt to free an anonymous device number that is not currently allocated. It happens in a different code path from the example below, at btrfs_get_root_ref(), so this change may not fix the case triggered by sy ---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
14th
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

April 4, 2024

Last Modified

August 5, 2026

Advisory Details (4)

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

btrfs: fix double free of anonymous device after snapshot creation failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix double free of anonymous device after snapshot creation failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix double free of anonymous device after snapshot creation failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: fix double free of anonymous device after snapshot creation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c34adc20b91a8e55e048b18d63f4f4ae003ecf8f

Vendor Advisories for CVE-2024-26792(1)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1030.34) @ jammy2026-10-28ubuntu
ubuntulinux-tools-kvm (5.15.0.1060.56) @ jammy2026-10-28ubuntu
ubuntulinux-tools-nvidia-lowlatency (5.15.0.1058.58) @ jammy2026-10-28ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1063.69~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1066.64) @ jammy2026-10-28ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.113.123~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1057.60~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.44.44) @ mantic2026-10-28ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1061.57) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp (6.5.0.1024.26~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-starfive (6.5.0.1017.18~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-10-28ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1027.29) @ jammy2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.44.44~22.04.1) @ jammy2026-10-28ubuntu
linuxKernel @ 6.1.81 (fixes >=6.1.79)—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

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 97 of 216 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 119 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% · 14th percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-28 07:24 UTCEG score recompute
  7. 2026-10-28 07:24 UTCVendor advisory
  8. 2026-10-28 07:23 UTCGHSA enrichmentGHSA-7w6v-jhvx-qx5c · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-25 17:15 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-10-20 20:18 UTCEG score recompute
  18. 2026-10-20 20:18 UTCVendor advisory
  19. 2026-10-20 20:18 UTCGHSA enrichmentGHSA-7w6v-jhvx-qx5c · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-10-19 19:55 UTCOSV refresh
  22. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-18 07:22 UTCEG score recompute
  25. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 72 more
  1. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-10-12 17:59 UTCEG score recompute
  6. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-10-11 21:23 UTCEG score recompute
  8. 2026-10-11 16:17 UTCEG score recompute
  9. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-09-30 16:59 UTCEG score recompute
  20. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-27 00:42 UTCOSV refresh
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  34. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-09-07 10:18 UTCOSV refresh
  37. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  38. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-20 19:31 UTCOSV refresh
  51. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  63. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-08-05 12:23 UTCEG score recompute
  65. 2026-08-05 12:23 UTCVendor advisory
  66. 2026-08-05 12:22 UTCGHSA enrichmentGHSA-7w6v-jhvx-qx5c · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-08-04 12:19 UTCEG score recompute
  69. 2026-08-04 12:19 UTCGHSA enrichmentGHSA-7w6v-jhvx-qx5c · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  71. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  72. 2026-08-01 08:06 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26792?
CVE-2024-26792 is a high-severity vulnerability; its CVE record was published on April 4, 2024. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of anonymous device after snapshot creation failure When creating a snapshot we may do a double free of an anonymous device in case there's an error committing the transaction. The second free may result in…
When was the CVE record for CVE-2024-26792 published?
The CVE record for CVE-2024-26792 was published on April 4, 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-26792 actively exploited?
CVE-2024-26792 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26792?
CVE-2024-26792 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26792?
A fix for CVE-2024-26792 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26792 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-26792

Explore →

Is Your Infrastructure Affected by CVE-2024-26792?

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

Book a Demo →Browse All CVEs