Skip to main content
VulnerabilityPublished Updated

CVE-2026-42015: gnutls. An off-by-one error exists · CWE-193

Source GCVE Database

0
Authoritative record:CVE-2026-42015· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
gnutlsAffected
  • =0
Fixed in–

AI-suggested

Red Hat has released updated gnutls packages for Red Hat Enterprise Linux 7 Extended Life Cycle Support that fix this vulnerability. Users should apply these official security updates as detailed in the Red Hat advisory (RHSA-2026:43575) to remediate the issue. Patch availability is confirmed and remediation is via official vendor updates.

Description

An off-by-one error in the PKCS#12 bag element bounds check in gnutls allows a remote attacker to write past the internal array when appending to a bag with 32 elements. This memory corruption can cause a denial of service (DoS) or potentially other unspecified impacts. The vulnerability is tracked as CVE-2026-42015 with a CVSS score of 5.3 (medium severity). Red Hat has released security updates addressing this issue in their Extended Life Cycle Support 7 packages.

References

Community reviews

Loading reviews…