# CVE-2026-110713: libsmb2 through 6.2 Heap Out-of-Bounds Read via File System Info Decoders

> A heap out-of-bounds read in libsmb2 allows malicious SMB servers to crash clients or read memory via crafted replies.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110713, GHSA-w2j6-hg6c-f9mp, UBUNTU-CVE-2026-110713

## What is CVE-2026-110713?

CVE-2026-110713 is a high-severity memory corruption vulnerability in sahlberg libsmb2, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

libsmb2 through 6.2 contains a heap out-of-bounds read vulnerability in smb2_decode_file_fs_volume_info and smb2_decode_file_fs_attribute_info that allows malicious SMB servers to read past reply buffers. Attackers controlling a server or intercepting unsigned sessions can send crafted QUERY_INFO replies with missing or oversized name lengths to crash the client.

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

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


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

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

## Is CVE-2026-110713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110713 is a high-severity memory corruption vulnerability in sahlberg libsmb2, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110713 exists.

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

## Sources

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

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