# CVE-2026-131849: Snap7 through 1.4.3 Heap-Based Buffer Overflow via TSnap7MicroClient::opReadSZL


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-68f4-569m-2rvc, UBUNTU-CVE-2026-131849

## What is CVE-2026-131849?

CVE-2026-131849 is a high-severity vulnerability in davenardella snap7, published on 17 Nov 2026. 

### Official description

Snap7 through 1.4.3 contains a heap-based buffer overflow in TSnap7MicroClient::opReadSZL() that allows malicious PLCs to overwrite client memory by sending oversized multi-slice SZL responses. A rogue or impersonated PLC can keep flagging more data with attacker-controlled DLen slices, overflowing the 65536-byte opData buffer via Cli_ReadSZL() and Cli_ReadSZLList(), crashing the client and corrupting heap memory.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

1 open source package ship an affected version, including davenardella/snap7.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `davenardella/snap7` | GitHub | `pkg:github/davenardella/snap7` | All versions to 1.4.3 | None |

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

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

## Is CVE-2026-131849 being exploited?

There is no known exploitation of CVE-2026-131849 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131849 is a high-severity vulnerability in davenardella snap7, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131849 in the wild and no public exploit code.

Affected packages and fixed versions:
- davenardella/snap7 (GitHub): affected all versions up to 1.4.3; no fix listed

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

## Sources

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

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