CVE-2026-55995

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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.7(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
Upstream fix merged — awaiting tagged release. 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
generic

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-55995

Vendor Advisories for CVE-2026-55995(1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatisns-utils-0:0.103-1.el10_2.12026-08-11redhat
redhatisns-utils-0:0.99-1.el8_10.12026-08-11redhat
redhatisns-utils-0:0.101-4.el9_8.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 rangeFixed inDependents
open-isns0.100-3 ... 0.103-2 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
open-isns0.101-0.2 ... 0.103-2 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
open-isns0.101-1, 0.101-2, 0.101-2.1, 0.103-1, 0.103-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
open-isns0.101-1, 0.101-2, 0.101-2.1, 0.103-10.103-2—

Weakness Classification(1)

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

All Vendor Advisories

(4)

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 36× in last 7d / 143× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 143 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55995?
CVE-2026-55995 is a high vulnerability 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 disclosed?
CVE-2026-55995 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55995 actively exploited?
CVE-2026-55995 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.6% of all scored CVEs.
What is the CVSS score of CVE-2026-55995?
CVE-2026-55995 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-55995?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55995, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs