CVE-2026-71225
Libkcapi: iv reuse in libkcapi one-shot symmetric cipher chunking causes cipher state reset across chunk boundaries
What happened?
A flaw was found in libkcapi. When performing one-shot symmetric cipher operations on large inputs (over 64 KiB) in stateful modes such as Counter (CTR) or Cipher Block Chaining (CBC), the library improperly reuses the Initialization Vector (IV) for each internal data chunk. A remote attacker could potentially exploit this by making an application that uses libkcapi process specially crafted large inputs. This can lead to a significant weakening of data confidentiality, as the repeated IV use can expose relationships in encrypted plaintext, and may also affect data integrity by causing incorrect cryptographic processing.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| libkcapiStephan Muelle | affected: 0.10.1 to < 1.5.1 | See vendor advisory |
| libkcapiRed Hat | unaffected: 0:1.5.1-1.el10_2 to < * | See vendor advisory |
| libkcapiRed Hat | unaffected: 0:1.5.0-6.el10_0 to < * | See vendor advisory |
| libkcapiRed Hat | unaffected: 0:1.4.0-3.el8_10 to < * | See vendor advisory |
| libkcapiRed Hat | unaffected: 0:1.4.0-3.el9_8 to < * | See vendor advisory |
| libkcapiRed Hat | unaffected: 0:1.4.0-2.el9_6.1 to < * | See vendor advisory |
| libkcapi-mainRed Hat | unaffected: 1.5.1-0.1.hum1 to < * | See vendor advisory |
| openshift/ose-rhel-coreos-8Red Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-71225
- https://access.redhat.com/errata/RHSA-2026:56985
- https://access.redhat.com/errata/RHSA-2026:67265
- https://access.redhat.com/errata/RHSA-2026:67266
- https://access.redhat.com/errata/RHSA-2026:67267
- https://access.redhat.com/errata/RHSA-2026:69285
- https://access.redhat.com/errata/RHSA-2026:87712
- https://access.redhat.com/security/cve/CVE-2026-71225
- https://bugzilla.redhat.com/show_bug.cgi?id=2462011