CVE-2026-43413

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2026-28719 (ENISA EUVD) · GHSA-3crh-xxfm-7qqg (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

scsi: hisi_sas: Fix NULL pointer exception during user_scan()

user_scan() invokes updated sas_user_scan() for channel 0, and if successful, iteratively scans remaining channels (1 to shost->max_channel) via scsi_scan_host_selected() in commit 37c4e72b0651 ("scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans"). However, hisi_sas supports only one channel, and the current value of max_channel is

  • sas_user_scan() for channel 1 will trigger the following NULL pointer
exception:

[ 441.554662] Unable to handle kernel NULL pointer dereference at virtual address 00000000000008b0 [ 441.554699] Mem abort info: [ 441.554710] ESR = 0x0000000096000004 [ 441.554718] EC = 0x25: DABT (current EL), IL = 32 bits [ 441.554723] SET = 0, FnV = 0 [ 441.554726] EA = 0, S1PTW = 0 [ 441.554730] FSC = 0x04: level 0 translation fault [ 441.554735] Data abort info: [ 441.554737] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 441.554742] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 441.554747] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 441.554752] user pgtable: 4k pages, 48-bit VAs, pgdp=00000828377a6000 [ 441.554757] [00000000000008b0] pgd=0000000000000000, p4d=0000000000000000 [ 441.554769] Internal error: Oops: 0000000096000004 [#1] SMP [ 441.629589] Modules linked in: arm_spe_pmu arm_smmuv3_pmu tpm_tis_spi hisi_uncore_sllc_pmu hisi_uncore_pa_pmu hisi_uncore_l3c_pmu hisi_uncore_hha_pmu hisi_uncore_ddrc_pmu hisi_uncore_cpa_pmu hns3_pmu hisi_ptt hisi_pcie_pmu tpm_tis_core spidev spi_hisi_sfc_v3xx hisi_uncore_pmu spi_dw_mmio fuse hclge hclge_common hisi_sec2 hisi_hpre hisi_zip hisi_qm hns3 hisi_sas_v3_hw sm3_ce sbsa_gwdt hnae3 hisi_sas_main uacce hisi_dma i2c_hisi dm_mirror dm_region_hash dm_log dm_mod [ 441.670819] CPU: 46 UID: 0 PID: 6994 Comm: bash Kdump: loaded Not tainted 7.0.0-rc2+ #84 PREEMPT [ 441.691327] pstate: 81400009 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) [ 441.698277] pc : sas_find_dev_by_rphy+0x44/0x118 [ 441.702896] lr : sas_find_dev_by_rphy+0x3c/0x118 [ 441.707502] sp : ffff80009abbba40 [ 441.710805] x29: ffff80009abbba40 x28: ffff082819a40008 x27: ffff082810c37c08 [ 441.717930] x26: ffff082810c37c28 x25: ffff082819a40290 x24: ffff082810c37c00 [ 441.725054] x23: 0000000000000000 x22: 0000000000000001 x21: ffff082819a40000 [ 441.732179] x20: ffff082819a40290 x19: 0000000000000000 x18: 0000000000000020 [ 441.739304] x17: 0000000000000000 x16: ffffb5dad6bda690 x15: 00000000ffffffff [ 441.746428] x14: ffff082814c3b26c x13: 00000000ffffffff x12: ffff082814c3b26a [ 441.753553] x11: 00000000000000c0 x10: 000000000000003a x9 : ffffb5dad5ea94f4 [ 441.760678] x8 : 000000000000003a x7 : ffff80009abbbab0 x6 : 0000000000000030 [ 441.767802] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 441.774926] x2 : ffff08280f35a300 x1 : ffffb5dad7127180 x0 : 0000000000000000 [ 441.782053] Call trace: [ 441.784488] sas_find_dev_by_rphy+0x44/0x118 (P) [ 441.789095] sas_target_alloc+0x24/0xb0 [ 441.792920] scsi_alloc_target+0x290/0x330 [ 441.797010] __scsi_scan_target+0x88/0x258 [ 441.801096] scsi_scan_channel+0x74/0xb8 [ 441.805008] scsi_scan_host_selected+0x170/0x188 [ 441.809615] sas_user_scan+0xfc/0x148 [ 441.813267] store_scan+0x10c/0x180 [ 441.816743] dev_attr_store+0x20/0x40 [ 441.820398] sysfs_kf_write+0x84/0xa8 [ 441.824054] kernfs_fop_write_iter+0x130/0x1c8 [ 441.828487] vfs_write+0x2c0/0x370 [ 441.831880] ksys_write+0x74/0x118 [ 441.835271] __arm64_sys_write+0x24/0x38 [ 441.839182] invoke_syscall+0x50/0x120 [ 441.842919] el0_svc_common.constprop.0+0xc8/0xf0 [ 441.847611] do_el0_svc+0x24/0x38 [ 441.850913] el0_svc+0x38/0x158 [ 441.854043] el0t_64_sync_handler+0xa0/0xe8 [ 441.858214] el0t_64_sync+0x1ac/0x1b0 [ 441.861865] Code: aa1303e0 97ff70a8 34ffff80 d10a4273 (f9445a75) [ 441.867946] ---[ end trace 0000000000000000 ]---

Therefore ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
1st
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 30, 2026

Advisory Details (5)

Auto-updated Jun 15, 2026
Patch available.
Web page

scsi: hisi_sas: Fix NULL pointer exception during user_scan() - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: hisi_sas: Fix NULL pointer exception during user_scan() - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: hisi_sas: Fix NULL pointer exception during user_scan() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70c78429ef383e35f9c58848994aeeac8083ae35
Web page

scsi: hisi_sas: Fix NULL pointer exception during user_scan() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40119a21d9769bf8fdab5c93c6c878296e628abf
Web page

scsi: hisi_sas: Fix NULL pointer exception during user_scan() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21a13db8d449b9c7eda4471da7f12417602dbbc7

Vendor Advisories for CVE-2026-43413(1)

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

Patch Availability(15)

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 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
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

(14)

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 100 of 235 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 135 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-43413?
CVE-2026-43413 is a medium-severity vulnerability; its CVE record was published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: hisisas: Fix NULL pointer exception during userscan() userscan() invokes updated sasuser_scan() for channel 0, and if successful, iteratively scans remaining channels (1 to shost->max_channel) via scsiscanhost_selected() in…
When was the CVE record for CVE-2026-43413 published?
The CVE record for CVE-2026-43413 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-43413 actively exploited?
CVE-2026-43413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43413?
CVE-2026-43413 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43413?
A fix for CVE-2026-43413 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43413 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-43413

Explore →

Is Your Infrastructure Affected by CVE-2026-43413?

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