CVE
Snap7 out-of-bounds write in multi-variable read
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
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround. The only exposure path they describe runs through Cli_ReadMultiVars, so limiting use of that call is the only measure they point to.
- 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? →
- 30/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 (vendor davenardella) through 1.4.3 has an out-of-bounds write flaw in its multi-variable read function, where data lengths from a PLC response are not checked before being copied into client buffers. An attacker who controls or impersonates a PLC can remotely, without logging in, send crafted responses that corrupt client memory and crash the client.
Written by a model from the sources below. Verify against them.
Original description
Snap7 through 1.4.3 contains an out-of-bounds write vulnerability in TSnap7MicroClient::opReadMultiVars() that allows malicious PLCs to overflow client buffers via unchecked DataLength fields. Attackers controlling or impersonating a PLC can return crafted ReadVar responses to Cli_ReadMultiVars() callers, writing up to 65535 bytes per item to corrupt memory and crash clients.
Who should check
Teams running snap7 1.4.3 or earlier as an S7 client, such as SCADA front ends, HMIs, historians and protocol gateways that call Cli_ReadMultiVars.
“Snap7 through 1.4.3 contains an out-of-bounds write vulnerability”
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 patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts give no workaround. The only exposure path they describe runs through Cli_ReadMultiVars, so limiting use of that call is the only measure they point to.
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-131848 (Snap7 through 1.4.3 Out-of-Bounds Write via TSnap7MicroClient::opReadMultiVars), 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-131848 (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 application calls Cli_ReadMultiVars, which uses TSnap7MicroClient::opReadMultiVars. (source: https://github.com/davenardella/snap7/issues/32)
- The peer PLC or server returns a crafted ReadVar response with an oversized per-item DataLength, reached on the first response. (source: https://github.com/davenardella/snap7/issues/32)
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-131848 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131848 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/issues/32
- https://github.com/davenardella/snap7/blob/30f37da3114024a71ba93f7fd855c680b97a406f/src/core/s7_micro_client.cpp#L400-L427
- https://www.vulncheck.com/advisories/snap7-through-1.4.3-out-of-bounds-write-via-tsnap7microclient-opreadmultivars
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-131848
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-131848"}.Timeline
- CVE published1 day
- First seen by cve.now
Affected versions
- davenardella snap7
through 1.4.3
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-131848
Is CVE-2026-131848 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 crafted ReadVar response from the peer PLC or server, with an oversized per-item DataLength, can make the client write up to 65535 bytes per item out of bounds. The write corrupts the client application's memory and can crash the client.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-131848?
snap7: through 1.4.3.Source: cve.now feed data
Am I affected, and how do I check?
Snap7 through 1.4.3 is listed as affected, with no earlier introduction point. The exposed path is an application that calls Cli_ReadMultiVars, which uses TSnap7MicroClient::opReadMultiVars, the batched read used for polling many tags. To check, look at the Snap7 version in use and search the application code for calls to Cli_ReadMultiVars.Source: github.com, vulncheck.com
How do I fix CVE-2026-131848?
The checked facts name no fixed version and no vendor patch identifiers, so no upgrade target can be given from them. Check the vendor's Snap7 release notes for a fixed version newer than 1.4.3.Source: github.com, vulncheck.com
What if there's no patch?
The checked facts give no workaround. The only exposure path they describe runs through Cli_ReadMultiVars, so limiting use of that call is the only measure they point to.Source: github.com, vulncheck.com