CVE-2026-71226

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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.

Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers.

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

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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 5, 2026

Last Modified

September 21, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
Patch available. Sources: redhat.
redhat

2462114 – (CVE-2026-71226) CVE-2026-71226 libkcapi: Memory corruption via uncanceled AIO requests on error in libkcapi's one-shot AIO path

https://bugzilla.redhat.com/show_bug.cgi?id=2462114
redhat Patch Available

CVE-2026-71226 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-71226

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatlibkcapi-0:1.5.0-6.el10_02026-09-21redhat
redhatlibkcapi-0:1.5.1-1.el10_22026-09-14redhat
redhatlibkcapi-0:1.4.0-3.el8_102026-09-14redhat
redhatlibkcapi-0:1.4.0-3.el9_82026-09-14redhat
redhatlibkcapi-main-1.5.1-0.1.hum12026-08-19redhat

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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi—
  • 0.12.0 up to 1.5.1-r0: fixed in 1.5.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi—
  • 0.12.0 up to 1.5.1-r0: fixed in 1.5.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi—
  • 0.12.0 up to 1.5.1-r0: fixed in 1.5.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi—
  • 0.12.0 up to 1.5.1-r0: fixed in 1.5.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi1.2.1-1 ... 1.4.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi1.4.0-1, 1.4.0-2, 1.5.1-1, 1.5.1-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi1.4.0-1, 1.4.0-2, 1.5.1-1, 1.5.1-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libkcapi1.4.0-1, 1.4.0-2
  • every version up to 1.5.1-1: fixed in 1.5.1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 132× 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 288 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-71226?
CVE-2026-71226 is a high vulnerability published on August 5, 2026. Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers.
When was CVE-2026-71226 disclosed?
CVE-2026-71226 was first published on August 5, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71226 actively exploited?
CVE-2026-71226 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71226?
CVE-2026-71226 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-71226?
A fix for CVE-2026-71226 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71226 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-71226

Explore →

Is Your Infrastructure Affected by CVE-2026-71226?

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