Findings

CVE-2023-25139

sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations with a correct buffer size.

Published Feb 3, 2023 · updated Oct 14, 2026 · gnu glibc

sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations with a correct buffer size. This is unrelated to CWE-676. It may write beyond the bounds of the destination buffer when attempting to write a padded, thousands-separated string representation of a number, if the buffer is allocated the exact size required to represent that number as a string. For example, 1,234,567 (with padding to 13) overflows by two bytes.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 3, 2023 · NIST NVD

    Detected

    sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations with a correct buffer size. This is unrelated to CWE-676. It may write beyond the bounds of the destination buffer when attempting to write a padded, thousands-separated string representation of a number, if the buffer is allocated the exact size required to represent that number as a string. F

  2. Oct 14, 2026 · NIST NVD

    Updated

    sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations with a correct buffer size. This is unrelated to CWE-676. It may write beyond the bounds of the destination buffer when attempting to write a padded, thousands-separated string representation of a number, if the buffer is allocated the exact size required to represent that number as a string. F

Affected

  • cpe gnu/glibc2.37

Sources

  • CVE.orgCVE-2023-25139

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2023-25139

    30-day exploitation probability 1.4%

    first.org
  • NIST NVDCVE-2023-25139

    sprintf in the GNU C Library (glibc) 2.37 has a buffer overflow (out-of-bounds write) in some situations with a correct buffer size. This is unrelated to CWE-676. It may write beyond the bounds of the destination buffer when attempting to write a padded, thousands-separated strin

    nvd.nist.gov

References

CVE-2023-25139 · ZeroDay Findings