CVE-2026-44944

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st 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-50312 (ENISA EUVD) · GHSA-jm64-8832-wmmq (GitHub Security Advisories)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An Incorrect Authorization vulnerability in open-iscsi allows unprivilidged local users to use the isscsiuio control socket.

This issue affects open-iscsi: from ? through 668ca1df9c9a1e9bdd5c999ae1d67c9c8909237e.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation<0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
<0.1%
EPSS %ILE
below the 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 (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 (CISA Vulnrichment) · Automatable no (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)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 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

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (2)

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

commit 668ca1df9c9a (open-iscsi/open-iscsi)

Patch available: open-iscsi/open-iscsi 2.1.12 (contains commit 668ca1df9c9a)

https://github.com/open-iscsi/open-iscsi/commit/668ca1df9c9a1e9bdd5c999ae1d67c9c8909237e
Web page

Making sure you're not a bot!

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

Vendor Advisories for CVE-2026-44944(5)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatiscsi-initiator-utils-0:6.2.1.4-3.git2a8f9d8.el9_2.22026-09-01redhat
redhatiscsi-initiator-utils-0:6.2.1.9-1.gita65a472.el9_6.32026-08-27redhat
redhatiscsi-initiator-utils-0:6.2.1.9-1.gita65a472.el9_4.22026-08-26redhat
redhatiscsi-initiator-utils-0:6.2.1.11-1.git4b3e853.el10_2.22026-08-11redhat
redhatiscsi-initiator-utils-0:6.2.1.11-1.git4b3e853.el9_8.22026-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-iscsi2.1.10-1 ... 2.1.9-4 (23 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
open-iscsi2.1.8-1
  • every version up to 2.1.8-1+deb12u1: fixed in 2.1.8-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
open-iscsi2.1.11-1 ... 2.1.13-1 (11 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
open-iscsi2.1.11-1 ... 2.1.11-6 (6 versions)
  • every version up to 2.1.12-1: fixed in 2.1.12-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 8× in last 7d / 46× 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 312 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 212 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:53844

Frequently asked(5)

What is CVE-2026-44944?
CVE-2026-44944 is a high-severity vulnerability; its CVE record was published on July 29, 2026. An Incorrect Authorization vulnerability in open-iscsi allows unprivilidged local users to use the isscsiuio control socket. This issue affects open-iscsi: from ? through 668ca1df9c9a1e9bdd5c999ae1d67c9c8909237e.
When was CVE-2026-44944 made public?
CVE-2026-44944 was made public on July 14, 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-44944 actively exploited?
CVE-2026-44944 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44944?
CVE-2026-44944 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44944?
A fix for CVE-2026-44944 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44944 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-44944

Explore →

Is Your Infrastructure Affected by CVE-2026-44944?

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

Book a Demo →Browse All CVEs