CVE-2026-23173

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-02-14. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2026-5866 (ENISA EUVD) · GHSA-5vr5-28pm-p634 (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:

net/mlx5e: TC, delete flows only for existing peers

When deleting TC steering flows, iterate only over actual devcom peers instead of assuming all possible ports exist. This avoids touching non-existent peers and ensures cleanup is limited to devices the driver is currently connected to.

BUG: kernel NULL pointer dereference, address: 0000000000000008 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 133c8a067 P4D 0 Oops: Oops: 0002 [#1] SMP CPU: 19 UID: 0 PID: 2169 Comm: tc Not tainted 6.18.0+ #156 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0xbe/0x200 [mlx5_core] Code: 00 00 a8 08 74 a8 49 8b 46 18 f6 c4 02 74 9f 4c 8d bf a0 12 00 00 4c 89 ff e8 0e e7 96 e1 49 8b 44 24 08 49 8b 0c 24 4c 89 ff <48> 89 41 08 48 89 08 49 89 2c 24 49 89 5c 24 08 e8 7d ce 96 e1 49 RSP: 0018:ff11000143867528 EFLAGS: 00010246 RAX: 0000000000000000 RBX: dead000000000122 RCX: 0000000000000000 RDX: ff11000143691580 RSI: ff110001026e5000 RDI: ff11000106f3d2a0 RBP: dead000000000100 R08: 00000000000003fd R09: 0000000000000002 R10: ff11000101c75690 R11: ff1100085faea178 R12: ff11000115f0ae78 R13: 0000000000000000 R14: ff11000115f0a800 R15: ff11000106f3d2a0 FS: 00007f35236bf740(0000) GS:ff110008dc809000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000008 CR3: 0000000157a01001 CR4: 0000000000373eb0 Call Trace: mlx5e_tc_del_flow+0x46/0x270 [mlx5_core] mlx5e_flow_put+0x25/0x50 [mlx5_core] mlx5e_delete_flower+0x2a6/0x3e0 [mlx5_core] tc_setup_cb_reoffload+0x20/0x80 fl_reoffload+0x26f/0x2f0 [cls_flower] ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core] ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core] tcf_block_playback_offloads+0x9e/0x1c0 tcf_block_unbind+0x7b/0xd0 tcf_block_setup+0x186/0x1d0 tcf_block_offload_cmd.isra.0+0xef/0x130 tcf_block_offload_unbind+0x43/0x70 __tcf_block_put+0x85/0x160 ingress_destroy+0x32/0x110 [sch_ingress] __qdisc_destroy+0x44/0x100 qdisc_graft+0x22b/0x610 tc_get_qdisc+0x183/0x4d0 rtnetlink_rcv_msg+0x2d7/0x3d0 ? rtnl_calcit.isra.0+0x100/0x100 netlink_rcv_skb+0x53/0x100 netlink_unicast+0x249/0x320 ? __alloc_skb+0x102/0x1f0 netlink_sendmsg+0x1e3/0x420 __sock_sendmsg+0x38/0x60 ____sys_sendmsg+0x1ef/0x230 ? copy_msghdr_from_user+0x6c/0xa0 ___sys_sendmsg+0x7f/0xc0 ? ___sys_recvmsg+0x8a/0xc0 ? __sys_sendto+0x119/0x180 __sys_sendmsg+0x61/0xb0 do_syscall_64+0x55/0x640 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f35238bb764 Code: 15 b9 86 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bf 0f 1f 44 00 00 f3 0f 1e fa 80 3d e5 08 0d 00 00 74 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 20 89 55 RSP: 002b:00007ffed4c35638 EFLAGS: 00000202 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 000055a2efcc75e0 RCX: 00007f35238bb764 RDX: 0000000000000000 RSI: 00007ffed4c356a0 RDI: 0000000000000003 RBP: 00007ffed4c35710 R08: 0000000000000010 R09: 00007f3523984b20 R10: 0000000000000004 R11: 0000000000000202 R12: 00007ffed4c35790 R13: 000000006947df8f R14: 000055a2efcc75e0 R15: 00007ffed4c35780

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
2nd
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-24). 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, 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; 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.

The score's inputs: 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

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (4)

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

net/mlx5e: TC, delete flows only for existing peers - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5e: TC, delete flows only for existing peers - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5e: TC, delete flows only for existing peers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62e1d8920f6920543f4b095a65fb964448c9901d
Web page

net/mlx5e: TC, delete flows only for existing peers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2652e2f1253c53f9a3ce84cc972568b32c892734

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-12ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-12ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-12ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-12ubuntu
linuxKernel @ 6.6.123 (fixes >=6.5.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
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)
  • every version up to 6.18.9-1: fixed in 6.18.9-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 7× in last 7d / 38× 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 99 of 221 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23173?
CVE-2026-23173 is a medium-severity vulnerability; its CVE record was published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: TC, delete flows only for existing peers When deleting TC steering flows, iterate only over actual devcom peers instead of assuming all possible ports exist. This avoids touching non-existent peers and ensures cleanup is…
When was the CVE record for CVE-2026-23173 published?
The CVE record for CVE-2026-23173 was published on February 14, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-23173 actively exploited?
CVE-2026-23173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23173?
CVE-2026-23173 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23173?
A fix for CVE-2026-23173 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-2026-23173

Explore →

Is Your Infrastructure Affected by CVE-2026-23173?

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

Book a Demo →Browse All CVEs