CVE-2026-42015: Gnutls: gnutls: memory corruption due to off-by-one error in pkcs#12 bag handling
A flaw was found in gnutls. An off-by-one error exists in the PKCS#12 bag element bounds check. This vulnerability allows an remote attacker to write past the internal array of a PKCS#12 bag when appending to a bag that already contains 32 elements. This memory corruption could lead to a denial of service (DoS) or potentially other unspecified impacts.
Security readout for executives and security teams
Plain-English summary
CVE-2026-42015 is a memory corruption flaw in GnuTLS PKCS#12 bag handling. A remote attacker could trigger a write just past an internal array when a bag already has 32 elements. The documented impact is denial of service, with other impacts unspecified.
Executive priority
Treat this as a routine but timely infrastructure patching item. It is remotely reachable and unauthenticated, but current public evidence points mainly to service disruption rather than confirmed compromise or active exploitation.
Technical view
The flaw is an off-by-one bounds check error, classified as CWE-193, in PKCS#12 bag element handling. Red Hat rates it medium with CVSS 3.1 score 5.3: network reachable, low complexity, no privileges or user interaction, unchanged scope, and low availability impact.
Likely exposure
Exposure is most relevant on affected Red Hat Enterprise Linux 8, 9, and 10 systems with gnutls or listed libtasn1 packages installed, especially where services process untrusted PKCS#12 data. Systems not using PKCS#12 processing have lower practical exposure.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. Public evidence supports a remote denial-of-service risk from memory corruption. The sources do not substantiate reliable code execution or broader impact beyond unspecified possibilities.
Researcher notes
Key uncertainty is exploitability beyond denial of service. The vulnerable condition involves appending to a PKCS#12 bag already containing 32 elements. Validation should focus on package inventory and reachable code paths, not broad assumptions that all TLS use is affected.
Mitigation direction
Apply the applicable Red Hat security advisory updates for affected gnutls and libtasn1 packages.
Prioritize exposed systems that process certificates, key stores, or PKCS#12 data from untrusted sources.
Check Red Hat CVE and RHSA pages for exact fixed package versions for each RHEL stream.
If updates are delayed, reduce or disable untrusted PKCS#12 processing where operationally feasible.
Validation and detection
Inventory RHEL 8, 9, and 10 systems for affected gnutls and libtasn1 package versions.
Map which applications or services invoke GnuTLS PKCS#12 import or bag handling paths.
Confirm installed package versions against the relevant Red Hat advisory for that OS stream.
Monitor crash, restart, or availability telemetry for services processing certificate bundles.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-193: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-193 · source CWE mapping
Off-by-one Error
Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.