CVE-2026-43406

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
Trending — 4 sources updated this week
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: prevent potential out-of-bounds reads in process_message_header()

If the message frame is (maliciously) corrupted in a way that the length of the control segment ends up being less than the size of the message header or a different frame is made to look like a message frame, out-of-bounds reads may ensue in process_message_header().

Perform an explicit bounds check before decoding the message header.

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
53rd
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-10-19). 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: 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.

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

October 19, 2026

Advisory Details (7)

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

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69fb5d91bba44ecf7eb80530b85fa4fb028921d5
Web page

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/035867ae6f18df0aeedb2a57a5b74091bd4e3fe8
Web page

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69fe5af33fa3806f398d21c081d73c66e5523bc2
Web page

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50156622eb0888e62541d715a98584480a1bc7cb
Web page

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75582aaa580c11aed4c7731cad6b068b700e7efb
Web page

libceph: prevent potential out-of-bounds reads in process_message_header() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76ccf21a12c5f6d6790bc32c7da82446d877b2f4

Vendor Advisories for CVE-2026-43406(1)

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

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1108.114~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-10-19ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-10-19ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-19ubuntu
ubuntuoracle (6.8.0-1005) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1116.101) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1106.112~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1074 (5.15.0-1074.78) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1017.19~24.04.1) @ noble2026-10-19ubuntu
linuxKernel @ 5.15.203 (fixes >=5.11.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

(3 across 3 ecosystems)
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 (123 versions)
  • every version up to 6.19.10-1: fixed in 6.19.10-1
—

Weakness Classification(1)

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

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

Frequently asked(5)

What is CVE-2026-43406?
CVE-2026-43406 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: prevent potential out-of-bounds reads in processmessageheader() If the message frame is (maliciously) corrupted in a way that the length of the control segment ends up being less than the size of the message header or a…
When was the CVE record for CVE-2026-43406 published?
The CVE record for CVE-2026-43406 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-43406 actively exploited?
CVE-2026-43406 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43406?
CVE-2026-43406 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-43406?
A fix for CVE-2026-43406 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43406 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-43406

Explore →

Is Your Infrastructure Affected by CVE-2026-43406?

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