CVE-2026-42015

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-05-27. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
50.3%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 22, 2026

Advisory Details (5)

Auto-updated Jun 16, 2026
Patch available. Sources: redhat.
redhat Patch Available

2467678 – (CVE-2026-42015) CVE-2026-42015 gnutls: gnutls: Memory corruption due to off-by-one error in PKCS#12 bag handling

Affected: Red Hat Enterprise Linux 8

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-42015
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:20613
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:20612
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:20611

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutls30t64 (3.8.12-2ubuntu1.1) @ resolute2026-07-01ubuntu
redhatgnutls-0:3.8.3-4.el9_4.62026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_4.12026-06-29redhat
redhatlibtasn1-0:4.13-4.el8_8.12026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_6.22026-06-29redhat
redhatgnutls-0:3.8.3-6.el9_6.42026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatgnutls-0:3.8.9-9.el10_0.192026-06-16redhat
redhatgnutls-0:3.8.10-4.el10_22026-05-26redhat
redhatgnutls-0:3.8.10-4.el9_82026-05-26redhat
redhatgnutls-0:3.6.16-8.el8_10.62026-05-26redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-42015?
CVE-2026-42015 is a medium vulnerability published on May 26, 2026. 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…
When was CVE-2026-42015 disclosed?
CVE-2026-42015 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42015 actively exploited?
CVE-2026-42015 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42015?
CVE-2026-42015 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-42015?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42015, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42015

Explore →

Is Your Infrastructure Affected by CVE-2026-42015?

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