Read the docs

Off-by-one buffer overflow in glibc wide scanf %s and %[ conversions

Priority LOW 22CWE-193Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · Low · Low
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

The GNU C Library (glibc) versions from 2.2 through 2.44 write one extra null byte past the end of the destination array when the wide scanf functions store a %s or %[ conversion without the l length modifier. The overflow happens because the terminating null byte is written twice, an off-by-one error (CWE-193). An attacker who supplies the input can trigger it with a string whose converted length exactly fills the destination, which may corrupt adjacent data or crash the process.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

Calling the wide scanf family of functions (swscanf, fwscanf, wscanf, vswscanf, vfwscanf and vwscanf) with a %s or %[ conversion without the 'l' length modifier in the GNU C Library version 2.2 to version 2.44 writes an extra null byte one past the end of the destination array when the converted multibyte string and its terminating null byte exactly fill that array. These conversions store each wide input character into the caller's char array as a multibyte sequence. The conversion ends with the sequence that returns to the initial shift state, which also stores the terminating null byte, and the functions then append a second null byte. A destination sized for the converted string and one terminator, as the C standard requires the caller to provide, is therefore written one byte past its end. The out-of-bounds byte is always a null byte, which may corrupt adjacent data or crash the process. An attacker who supplies the input can trigger the overflow with a string whose converted length exactly fills the destination. The narrow scanf functions, the %ls and %l[ conversions into a wchar_t array, and the 'a' and 'm' allocation modifiers are not affected, and storing a wide scanf conversion into a narrow char array is uncommon. This issue affects all architectures and ABIs supported by the GNU C Library.

Why it matters now

EPSS 0.00263 18th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
GNUglibc2.2 – 2.44—No fix listedCNA
  • glibc VendorGNU Affected 2.2 – 2.44 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*——GNU
  • cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:* Versions — — ·GNU

Remediation

The sources list no fixed version for glibc.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-115819
  2. 2026-11-11 Alias added: GHSA-rm44-gpwr-xh4q

References

  • TI-2026-19388 Authentication bypass in GNU Inetutils telnetd via USER variable KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05975 GNU Bash environment variable parsing flaw lets attackers write files KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05157 Code execution in GNU Bash through crafted environment variables KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05164 Command injection in GNU Bash via crafted environment variables KEVCVSS 3.1HIGH 8.8
  • TI-2023-04522 Buffer overflow in glibc ld.so allows privilege escalation KEVCVSS 3.1HIGH 7.8
  • TI-2009-03392 The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft… CVSS 3.1CRITICAL 9.8
See all 1274 →

Sources