CVE-2026-43407

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-08. NVD baseline CVSS 9.1; sources differ by 0.0.

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

Also known asEUVD-2026-28713 (ENISA EUVD) · GHSA-g5m7-8jmr-xx94 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply()

This patch fixes an out-of-bounds access in ceph_handle_auth_reply() that can be triggered by a message of type CEPH_MSG_AUTH_REPLY. In ceph_handle_auth_reply(), the value of the payload_len field of such a message is stored in a variable of type int. A value greater than INT_MAX leads to an integer overflow and is interpreted as a negative value. This leads to decrementing the pointer address by this value and subsequently accessing it because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation.

This patch fixes the issue by changing the data type of payload_len to u32. Additionally, the data type of result_msg_len is changed to u32, as it is also a variable holding a non-negative length.

Also, an additional layer of sanity checks is introduced, ensuring that directly after reading it from the message, payload_len and result_msg_len are not greater than the overall segment length.

BUG: KASAN: slab-out-of-bounds in ceph_handle_auth_reply+0x642/0x7a0 [libceph] Read of size 4 at addr ffff88811404df14 by task kworker/20:1/262

CPU: 20 UID: 0 PID: 262 Comm: kworker/20:1 Not tainted 6.19.2 #5 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: ceph-msgr ceph_con_workfn [libceph] Call Trace: dump_stack_lvl+0x76/0xa0 print_report+0xd1/0x620 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? kasan_complete_mode_report_info+0x72/0x210 kasan_report+0xe7/0x130 ? ceph_handle_auth_reply+0x642/0x7a0 [libceph] ? ceph_handle_auth_reply+0x642/0x7a0 [libceph] __asan_report_load_n_noabort+0xf/0x20 ceph_handle_auth_reply+0x642/0x7a0 [libceph] mon_dispatch+0x973/0x23d0 [libceph] ? apparmor_socket_recvmsg+0x6b/0xa0 ? __pfx_mon_dispatch+0x10/0x10 [libceph] ? __kasan_check_write+0x14/0x30i ? mutex_unlock+0x7f/0xd0 ? __pfx_mutex_unlock+0x10/0x10 ? __pfx_do_recvmsg+0x10/0x10 [libceph] ceph_con_process_message+0x1f1/0x650 [libceph] process_message+0x1e/0x450 [libceph] ceph_con_v2_try_read+0x2e48/0x6c80 [libceph] ? __pfx_ceph_con_v2_try_read+0x10/0x10 [libceph] ? save_fpregs_to_fpstate+0xb0/0x230 ? raw_spin_rq_unlock+0x17/0xa0 ? finish_task_switch.isra.0+0x13b/0x760 ? __switch_to+0x385/0xda0 ? __kasan_check_write+0x14/0x30 ? mutex_lock+0x8d/0xe0 ? __pfx_mutex_lock+0x10/0x10 ceph_con_workfn+0x248/0x10c0 [libceph] process_one_work+0x629/0xf80 ? __kasan_check_write+0x14/0x30 worker_thread+0x87f/0x1570 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? __pfx_try_to_wake_up+0x10/0x10 ? kasan_print_address_stack_frame+0x1f7/0x280 ? __pfx_worker_thread+0x10/0x10 kthread+0x396/0x830 ? __pfx__raw_spin_lock_irq+0x10/0x10 ? __pfx_kthread+0x10/0x10 ? __kasan_check_write+0x14/0x30 ? recalc_sigpending+0x180/0x210 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x3f7/0x610 ? __pfx_ret_from_fork+0x10/0x10 ? __switch_to+0x385/0xda0 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

[ idryomov: replace if statements with ceph_decode_need() for payload_len and result_msg_len ]

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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: 14 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 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)14 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 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

May 8, 2026

Last Modified

November 11, 2026

Advisory Details (8)

Auto-updated Sep 16, 2026
Patch available.
Web page

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8bb87547e92dcf0928ed763c60e0ac8d733c3656
Web page

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6cee34d6669fe176b4259131adb1a145c939b472
Web page

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-43407(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-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-11-11ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-11-11ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-11-11ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1116.101) @ jammy2026-11-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-11-11ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-11-11ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-11-11ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1074 (5.15.0-1074.78) @ jammy2026-11-11ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-11-11ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-11-11ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-11-11ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-11-11ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-11-11ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.233.253~18.04.1) @ bionic2026-11-11ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-11-11ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-11-11ubuntu
ubuntulinux-tools-fips (4.4.0.1126.128) @ xenial2026-11-11ubuntu
ubuntulinux-tools-aws-lts-18.04 (4.15.0.1194.192) @ bionic2026-11-11ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-11-11ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1106.112~20.04.1) @ focal2026-11-11ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-11-11ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-11-11ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.254.266~16.04.1) @ xenial2026-11-11ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1017.19) @ questing2026-11-11ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-11-11ubuntu
ubuntulinux-virtual (3.13.0.214.224) @ trusty2026-11-11ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1107.136) @ focal2026-11-11ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1144.175) @ focal2026-11-11ubuntu
ubuntulinux-tools-aws-hwe (4.15.0.1195.208~16.04.1) @ xenial2026-11-11ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.283.289) @ xenial2026-11-11ubuntu
linuxKernel @ 5.10.253 (fixes >=2.6.34)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)
  • every version up to 6.19.10-1: fixed in 6.19.10-1
—

Weakness Classification(2)

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

All Vendor Advisories

(25)

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 15× in last 7d / 82× 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 490 rows 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 390 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)· as of November 11, 2026

Frequently asked(5)

What is CVE-2026-43407?
CVE-2026-43407 is a critical-severity vulnerability; its CVE record was published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() This patch fixes an out-of-bounds access in ceph_handle_auth_reply() that can be triggered by a message of type CEPH_MSG_AUTH_REPLY. In…
When was the CVE record for CVE-2026-43407 published?
The CVE record for CVE-2026-43407 was published on May 8, 2026. 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 11, 2026; the record at its source may have been updated since.
Is CVE-2026-43407 actively exploited?
CVE-2026-43407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43407?
CVE-2026-43407 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-43407?
A fix for CVE-2026-43407 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43407 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-2026-43407

Explore →

Is Your Infrastructure Affected by CVE-2026-43407?

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

Book a Demo →Browse All CVEs