# CVE-2026-112274: libtins through 4.6 Out-of-Bounds Read via DNS::soa_record::init

> Remote attackers can trigger out-of-bounds reads and potential crashes in libtins by sending malformed DNS SOA records lacking null terminators.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112274, GHSA-4c37-573g-qpf9, UBUNTU-CVE-2026-112274

## What is CVE-2026-112274?

CVE-2026-112274 is a medium-severity vulnerability in libtins, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libtins through 4.6 contains an out-of-bounds read vulnerability in DNS::soa_record::init that allows remote attackers to read past buffer bounds by supplying SOA data lacking NUL terminators. Attackers can feed raw SOA RDATA without a zero byte to applications using the buffer constructor, causing strlen to overrun the heap buffer and possibly crash.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-112274?


## How do I fix CVE-2026-112274?

No fix has been published for CVE-2026-112274 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112274 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112274 and fix it if it is affected.

What it is: CVE-2026-112274 is a medium-severity vulnerability in libtins, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112274 exists.

Affected product: libtins. 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-2026-112274/ (Markdown: https://insights.sbomify.com/CVE-2026-112274/index.md)
```

## Sources

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

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