CVE
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.
Written by a model from the sources below. Verify against them.
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
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Original 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.
Who should check
Teams running snap7 1.4.3 or earlier that read SZL data from PLCs via Cli_ReadSZL or Cli_ReadSZLList
“Affecting snap7 <= 1.4.3”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published1 day
- First seen by cve.now
Affected versions
- davenardella snap7
through 1.4.3
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Patch
- Report
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-131849
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-131849?
snap7: through 1.4.3.Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com