CVE-2026-79619

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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
7.3EG
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.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

On Linux, several OpenZFS ioctl authorization checks accept a capability held only within a user-created, unprivileged namespace as equivalent to real host privilege, allowing an unprivileged local user to perform operations that should require root. Affected operations include pool-administrative operations (eg create, import, destroy), pool event log access (zpool events) and fault injection (zinject). Exploiting the problem requires only that the local user is permitted to open /dev/zfs (governed by local device permissions) and that the kernel permits unprivileged user namespace creation. No prior access to the target pool or its underlying devices is needed.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.2% × 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.2%
EPSS %ILE
8th
KEV
Not listed

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.

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

August 26, 2026

Last Modified

August 28, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
Patch available. Sources: github_release, github_pr.
GitHub release Patch Available

zfs-2.2.11

Patch available: openzfs/zfs zfs-2.2.11

https://github.com/openzfs/zfs/releases/tag/zfs-2.2.11
GitHub release Patch Available

zfs-2.3.9

Patch available: openzfs/zfs zfs-2.3.9

https://github.com/openzfs/zfs/releases/tag/zfs-2.3.9
GitHub release Patch Available

zfs-2.4.4

Patch available: openzfs/zfs zfs-2.4.4

https://github.com/openzfs/zfs/releases/tag/zfs-2.4.4
GitHub pull request

Linux: tighten secpolicy zone checks

Upstream fix in progress (PR #18959 · openzfs/zfs, state=closed)

https://github.com/openzfs/zfs/pull/18959

Vendor Advisories for CVE-2026-79619(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuzfsutils-linux (2.4.1-1ubuntu5.1) @ resolute2026-10-08ubuntu
ubuntuzfsutils-linux (0.8.3-1ubuntu12.18+esm1) @ focal2026-10-08ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
zfs-linux0.6.5.10-1 ... 2.4.4-1~bpo13+1 (213 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
zfs-linux0.6.5.10-1 ... 2.3.5-2~bpo13+1 (197 versions)
  • every version up to 2.3.9-0+deb13u1: fixed in 2.3.9-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
zfs-linux0.6.5.10-1 ... 2.4.4-1~bpo13+1 (211 versions)
  • every version up to 2.4.4-1: fixed in 2.4.4-1
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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

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

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:12:zfs-linux

Frequently asked(5)

What is CVE-2026-79619?
CVE-2026-79619 is a high-severity vulnerability; its CVE record was published on August 26, 2026. On Linux, several OpenZFS ioctl authorization checks accept a capability held only within a user-created, unprivileged namespace as equivalent to real host privilege, allowing an unprivileged local user to perform operations that should require root. Affected operations include pool-administrative…
When was the CVE record for CVE-2026-79619 published?
The CVE record for CVE-2026-79619 was published on August 26, 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 August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-79619 actively exploited?
CVE-2026-79619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79619?
CVE-2026-79619 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79619?
A fix for CVE-2026-79619 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79619 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-79619

Explore →

Is Your Infrastructure Affected by CVE-2026-79619?

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

Book a Demo →Browse All CVEs