Quick answers
- Is CVE-2026-5450 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5450 being exploited in the wild.
- How severe is CVE-2026-5450?
- Critical severity, with a CVSS score of 9.8, published 20 April 2026.
- Which products and versions are affected?
- Gnu Glibc 2.7 to 2.43; Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP V3.1.5; Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP V3.1.5; Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP V3.1.5.
- Is there a fix for CVE-2026-5450?
- A patch was published on 2026-05-08: Fix committed to glibc master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-5450 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-5450?
- Check whether you run Gnu Glibc, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A one-byte heap buffer overflow exists in glibc's __vfscanf_internal function due to an incorrect buffer growth formula. When the scanf family of functions is called with the %mc (malloc'd character match) or %mC specifier and an explicit format width greater than 1024, the realloc expansion under-allocates by one byte. An attacker providing controlled input to an application using this specific format specifier can trigger a single-byte overwrite past the end of the heap buffer, potentially leading to arbitrary code execution. The vulnerability affects glibc versions 2.7 through 2.43 and has been addressed in version 2.44.
Affected products
- GNU glibc 2.7 to 2.43
- Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP V3.1.5
- Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP V3.1.5
- Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP V3.1.5
Timeline
- 2026-03-19: disclosed: Reported by Rocket Ma
- 2026-04-20: advisory: Initial NVD publication and glibc security advisory GLIBC-SA-2026-0009
- 2026-05-08: patched: Fix committed to glibc master branch