Libinih: inih before r63 contains a one-byte stack buffer under-read in ini_parse_stream() in ini.c that allows
Affects libinihSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium.
Data as of 5 Nov 2026, 12:34 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 4.8 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.3 |
| CNA | CVSS 4.0 | 4.8 |
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libinihpkg:deb/ubuntu/libinih?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibinihpkg:deb/ubuntu/libinih?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibinihpkg:deb/ubuntu/libinih?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlibinihpkg:deb/ubuntu/libinih?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSlibinihpkg:deb/ubuntu/libinih?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSlibinihpkg:deb/ubuntu/libinih?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
inih before r63 contains a one-byte stack buffer under-read in ini_parse_stream() in ini.c that allows attackers to read abyss[-1] via an embedded NUL byte after an overlong line. Attackers can supply an INI file or string with a line of at least INI_MAX_LINE-1 bytes followed by a NUL byte, causing undefined behavior reported by memory sanitizers.
References
- ubuntu.com/security/CVE-2025-71450 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-71450 (opens in a new tab)
- github.com/benhoyt/inih/blob/r62/ini.c (opens in a new tab)
- github.com/benhoyt/inih/commit/8e06f6b77b5d4471bdc6d85ada81b67d37354a5c (opens in a new tab)
- github.com/benhoyt/inih/issues/223 (opens in a new tab)
- github.com/benhoyt/inih/pull/206 (opens in a new tab)
- github.com/benhoyt/inih/releases/tag/r63 (opens in a new tab)
- hackmd.io/@haindpwn/inih-long-line-discard-oob-read (opens in a new tab)
- vulncheck.com/advisories/inih-before-r63-stack-buffer-under-read-in-ini-parse-stream-discard-loop (opens in a new tab)