CVE-2026-55995

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-50330 (ENISA EUVD) · GHSA-93fw-mwmg-2g5m (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

A Double Free vulnerability in open-iscsi allows an unauthenticated MITM attacker to cause DoS.

This issue affects open-iscsi: from ? through 56718d4e9d1a4f51c30697b5c0534144bb41c9bb.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.3%
EPSS %ILE
16th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
Patch available. Sources: github_commit.
GitHub commit

commit 56718d4e9d1a (open-iscsi/open-isns)

Fix landed in open-iscsi/open-isns commit 56718d4e9d1a — awaiting tagged release

https://github.com/open-iscsi/open-isns/commit/56718d4e9d1a4f51c30697b5c0534144bb41c9bb

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopen-isns-utils (0.101-2.1ubuntu0.1) @ resolute2026-10-24ubuntu
redhatisns-utils-0:0.99-1.el8_4.12026-08-31redhat
redhatisns-utils-0:0.99-1.el8_6.12026-08-26redhat
redhatisns-utils-0:0.99-1.el8_8.12026-08-26redhat
redhatisns-utils-0:0.101-4.el9_4.12026-08-26redhat
redhatisns-utils-0:0.101-4.el9_6.12026-08-26redhat
redhatisns-utils-0:0.101-4.el9_2.12026-08-26redhat
redhatisns-utils-0:0.103-1.el10_0.12026-08-26redhat
redhatisns-utils-0:0.99-1.el8_10.12026-08-11redhat
redhatisns-utils-0:0.101-4.el9_8.12026-08-11redhat
redhatisns-utils-0:0.103-1.el10_2.12026-08-11redhat

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
open-isns0.100-3 ... 0.103-2 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
open-isns0.101-0.2 ... 0.103-2 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
open-isns0.101-1, 0.101-2, 0.101-2.1, 0.103-1, 0.103-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
open-isns0.101-1, 0.101-2, 0.101-2.1, 0.103-1
  • every version up to 0.103-2: fixed in 0.103-2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 57× 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 340 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 240 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.3% · 16th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-31 00:03 UTCEG score recompute
  4. 2026-10-31 00:03 UTCVendor advisory
  5. 2026-10-31 00:03 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-25 14:18 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  14. 2026-10-24 01:37 UTCEG score recompute
  15. 2026-10-24 01:37 UTCVendor advisory
  16. 2026-10-24 01:37 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  17. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-10-18 03:29 UTCEG score recompute
  24. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-10-17 03:10 UTCEG score recompute
Show 75 more
  1. 2026-10-17 03:10 UTCVendor advisory
  2. 2026-10-17 03:10 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  3. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  4. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  5. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  6. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-12 15:55 UTCEG score recompute
  9. 2026-10-11 19:38 UTCEG score recompute
  10. 2026-10-11 16:53 UTCEG score recompute
  11. 2026-10-11 14:16 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-07 00:01 UTCEG score recompute
  18. 2026-10-07 00:01 UTCVendor advisory
  19. 2026-10-07 00:01 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-05 20:53 UTCEG score recompute
  22. 2026-10-05 20:53 UTCVendor advisory
  23. 2026-10-05 20:53 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-10-05 02:37 UTCEG score recompute
  26. 2026-10-05 02:37 UTCVendor advisory
  27. 2026-10-05 02:37 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  28. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-10-04 07:02 UTCEG score recompute
  30. 2026-10-04 07:02 UTCVendor advisory
  31. 2026-10-04 07:02 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  32. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-10-02 17:58 UTCEG score recompute
  34. 2026-10-02 17:58 UTCVendor advisory
  35. 2026-10-02 17:58 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  36. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-10-01 15:43 UTCVendor advisory
  39. 2026-10-01 15:43 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  40. 2026-10-01 03:36 UTCEG score recompute
  41. 2026-10-01 03:36 UTCVendor advisory
  42. 2026-10-01 03:36 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  43. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  44. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-09-29 07:36 UTCEG score recompute
  46. 2026-09-29 07:36 UTCVendor advisory
  47. 2026-09-29 07:36 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  48. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-09-28 03:17 UTCEG score recompute
  50. 2026-09-28 03:17 UTCVendor advisory
  51. 2026-09-28 03:17 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  52. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-09-25 05:41 UTCEG score recompute
  55. 2026-09-25 05:41 UTCVendor advisory
  56. 2026-09-25 05:41 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  57. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-09-24 09:52 UTCVendor advisory
  59. 2026-09-24 09:52 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  60. 2026-09-23 21:50 UTCEG score recompute
  61. 2026-09-23 21:50 UTCVendor advisory
  62. 2026-09-23 21:50 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  63. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  64. 2026-09-23 03:52 UTCVendor advisory
  65. 2026-09-23 03:52 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  66. 2026-09-22 15:49 UTCEG score recompute
  67. 2026-09-22 15:49 UTCVendor advisory
  68. 2026-09-22 15:49 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  69. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  70. 2026-09-20 00:23 UTCEG score recompute
  71. 2026-09-20 00:23 UTCVendor advisory
  72. 2026-09-20 00:23 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH
  73. 2026-09-19 04:55 UTCEG score recompute
  74. 2026-09-19 04:55 UTCVendor advisory
  75. 2026-09-19 04:55 UTCGHSA enrichmentGHSA-93fw-mwmg-2g5m · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-55995?
CVE-2026-55995 is a high-severity vulnerability; its CVE record was published on July 29, 2026. A Double Free vulnerability in open-iscsi allows an unauthenticated MITM attacker to cause DoS. This issue affects open-iscsi: from ? through 56718d4e9d1a4f51c30697b5c0534144bb41c9bb.
When was CVE-2026-55995 made public?
CVE-2026-55995 was made public on July 28, 2026: that is the date its CVE record's CNA, SUSE, gives for when the vulnerability was made public. The CVE record itself was published on July 29, 2026. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-55995 actively exploited?
CVE-2026-55995 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55995?
CVE-2026-55995 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55995?
A fix for CVE-2026-55995 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55995 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-55995

Explore →

Is Your Infrastructure Affected by CVE-2026-55995?

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