# CVE-2025-71450: inih before r63 Stack Buffer Under-Read in ini_parse_stream Discard Loop


- **Severity:** Medium 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:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** BELL-CVE-2025-71450, GHSA-gh7m-xpp3-w3vq, UBUNTU-CVE-2025-71450, openSUSE-SU-2026:12432-1

## What is CVE-2025-71450?

CVE-2025-71450 is a medium-severity vulnerability in benhoyt inih, published on 2 Nov 2026. 

### Official 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.

Weakness: CWE-127 (Buffer Under-read)

## Which versions are affected by CVE-2025-71450?


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `inih` | openSUSE:Tumbleweed | `pkg:rpm/opensuse/inih` | All versions | 63-1.1 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| openSUSE | Tumbleweed | fixed | `inih` | 63-1.1 |

## How do I fix CVE-2025-71450?

Upgrade to a fixed version.

## Is CVE-2025-71450 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71450 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71450 and fix it if it is affected.

What it is: CVE-2025-71450 is a medium-severity vulnerability in benhoyt inih, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71450 exists.

Affected product: benhoyt inih. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-71450/ (Markdown: https://insights.sbomify.com/CVE-2025-71450/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-71450
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-71450
- OSV: https://osv.dev/vulnerability/CVE-2025-71450

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-71450/
Summaries are generated and may contain mistakes; the official description above is the record.
