CVE-2026-74556

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-59621 (ENISA EUVD) · GHSA-2m3x-37gx-2chv (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer

iscsi_tcp_hdr_dissect() receives the data segment of several PDU types into the fixed-size conn->data buffer, which is allocated for ISCSI_DEF_MAX_RECV_SEG_LEN (8192) bytes. For the LOGIN_RSP, TEXT_RSP, REJECT and ASYNC_EVENT opcodes the dissect path already rejects a PDU whose DataSegmentLength exceeds that buffer.

The SCSI Command Response (ISCSI_OP_SCSI_CMD_RSP) path also copies its data segment (sense/response data) into conn->data via iscsi_tcp_data_recv_prep(), but it does so without the same check. The only upstream bound on in.datalen is conn->max_recv_dlength, the initiator's advertised MaxRecvDataSegmentLength, which is commonly negotiated well above 8192 (open-iscsi defaults to 262144). A target that returns a SCSI Response with a DataSegmentLength between 8193 and max_recv_dlength therefore overflows the 8192-byte conn->data buffer.

Once the same bound applies, ISCSI_OP_SCSI_CMD_RSP is handled exactly like those responses: bound the data segment, receive it into conn->data when present, and otherwise complete the PDU with no data. Fold the opcode into that case group rather than duplicating the check.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 total (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.4%
EPSS %ILE
34th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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: 3 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 total (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)3 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 total (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

August 15, 2026

Last Modified

October 16, 2026

Advisory Details (8)

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72815741715bd41556dac5eeb068bf0f8af06ee7
Web page

scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/084af0253673425ce2ae62e3c7f74f0dd023711b

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-477.179.1.el8_82026-11-20redhat
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-11-19ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1064.65) @ noble2026-11-19ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-19ubuntu
ubuntulinux-vmware-tools-6.8.0-1010 (6.8.0-1010.10) @ noble2026-11-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-19ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute2026-11-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-11-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-11-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-11-19ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1113.111) @ jammy2026-11-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-11-19ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-19ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1067.71~22.04.1) @ jammy2026-11-19ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1071.78) @ noble2026-11-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1070.70) @ jammy2026-11-19ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1016.18~24.04.1) @ noble2026-11-19ubuntu
redhatkernel-0:5.14.0-284.202.1.el9_22026-11-03redhat
redhatkernel-rt-0:5.14.0-284.202.1.rt14.487.el9_22026-11-03redhat
redhatkernel-0:6.12.0-55.117.1.el10_02026-11-03redhat
redhatkernel-0:5.14.0-427.161.1.el9_42026-11-02redhat
redhatkernel-0:5.14.0-570.152.1.el9_62026-10-28redhat
redhatkernel-0:4.18.0-305.211.1.el8_42026-10-07redhat
redhatkernel-0:4.18.0-372.220.1.el8_62026-10-07redhat
redhatkernel-rt-0:4.18.0-553.163.1.rt7.504.el8_102026-09-15redhat
redhatkernel-0:4.18.0-553.163.1.el8_102026-09-15redhat
redhatkernel-0:5.14.0-687.48.1.el9_82026-09-15redhat
redhatkernel-0:6.12.0-211.55.1.el10_22026-09-15redhat
linuxKernel @ 5.10.265 (fixes >=2.6.29)—osv

These rows come from Red Hat, Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (166 versions)
  • every version up to 7.1.8-1: fixed in 7.1.8-1
—

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 20× in last 7d / 91× 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 625 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 525 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-74556?
CVE-2026-74556 is a critical-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer iscsi_tcp_hdr_dissect() receives the data segment of several PDU types into the fixed-size conn->data buffer, which is allocated for…
When was the CVE record for CVE-2026-74556 published?
The CVE record for CVE-2026-74556 was published on August 15, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-74556 actively exploited?
CVE-2026-74556 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74556?
CVE-2026-74556 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74556?
A fix for CVE-2026-74556 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74556 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-74556

Explore →

Is Your Infrastructure Affected by CVE-2026-74556?

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