Skip to main content
VulnerabilityPublished

CVE-2026-97399: The GNU C Library glibc · Buffer Over-read

Affects The GNU C Library glibcSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low : upgrade to 2.45 when convenient.

Data as of 12 Nov 2026, 23:25 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.45
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 13 Nov 2026.

What to do

Upgrade glibc and the Debian debian/glibc package to 2.45.

Affected software

ProductAffectedFixed in
The GNU C LibraryglibcAffected
  • >=2.24 <2.45
Fixed in
  • 2.45
Debiandebian/glibcpkg:deb/debian/glibcOther threatsAffected
  • >=2.24 <2.45
Fixed in
  • 2.45

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, applications using glibc on Power8 architecture should consider avoiding attacker-controlled inputs that could trigger this condition or apply other application-level mitigations to prevent crashes.

Description

The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable. This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.

References

Community reviews

Loading reviews…