Skip to content
Fencer Vulns
critical 9.8

CVE-2018-13876 json

An issue was discovered in the HDF HDF5 1.8.20 library.

published 2018-07-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-5810

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

An issue was discovered in the HDF HDF5 1.8.20 library. There is a stack-based buffer overflow in the function H5FD_sec2_read in H5FDsec2.c, related to HDread.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-13876 updated cvss 7.0

hdf5: stack-based buffer overflow in the function H5FD_sec2_read in H5FDsec2.c

  • Red Hat Enterprise Linux 8 hdf5 Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) hdf5 Red Hat OpenStack Platform 8 (Liberty) hdf5 Red Hat OpenStack Platform 9 (Mitaka) hdf5 Red Hat OpenStack Platform 10 (Newton) hdf5
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 12 (Pike) hdf5
    affected: no fix available
  • Red Hat OpenStack Platform 13 (Queens) hdf5 Red Hat OpenStack Platform 14 (Rocky) hdf5
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.30% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/TeamSeri0us/pocs/tree/master/hdf5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.