VulnerabilityPublished 14 Dec 2025Updated 24 Feb 2026

CVE-2025-14672: gmg137 snap7-rs · Heap-based Buffer Overflow

Affects gmg137 snap7-rsSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubgmg137/snap7-rs`pkg:github/gmg137/snap7-rs`Other threats	Affected =1.142.0 =1.142.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately audit and inventory all systems using snap7-rs versions 1.142.0 and 1.142.1 to identify vulnerable instances.
Restrict network access to snap7-rs services by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only.
Employ intrusion detection and prevention systems (IDS/IPS) with signatures or anomaly detection tuned to snap7-rs protocol anomalies to detect exploitation attempts.
Monitor network traffic for unusual or malformed packets targeting the opWriteArea function or snap7-rs communication ports.
Disable or limit remote write operations via snap7-rs if not required, reducing the attack surface.
Engage with the vendor or open-source maintainers to obtain or contribute patches addressing the heap overflow.
Consider deploying application-layer gateways or protocol proxies that validate and sanitize snap7-rs traffic.
Implement robust logging and alerting on snap7-rs client activities to facilitate rapid incident response.
Prepare incident response plans specific to ICS/PLC compromise scenarios.
Stay informed on updates and apply patches promptly once available.

Description

A flaw has been found in gmg137 snap7-rs up to 1.142.1. This impacts the function TSnap7MicroClient::opWriteArea of the file s7_micro_client.cpp. Executing a manipulation can lead to heap-based buffer overflow. It is possible to launch the attack remotely. The exploit has been published and may be used.

Impact

The vulnerability poses a medium-severity risk but with potentially serious consequences for organizations using snap7-rs in industrial automation. Successful exploitation could lead to unauthorized remote code execution, allowing attackers to disrupt industrial processes, manipulate control commands, or cause denial of service conditions. This could result in operational downtime, safety hazards, data corruption, and loss of control over critical infrastructure. The partial impact on confidentiality could expose sensitive operational data or intellectual property. Given the remote exploitability without authentication, attackers can target exposed snap7-rs instances over the network, increasing the attack surface. The availability of a public exploit increases the likelihood of attacks, especially by opportunistic or less sophisticated adversaries. Organizations in manufacturing, energy, utilities, and critical infrastructure sectors that rely on Siemens PLCs and snap7-rs are particularly vulnerable. The absence of patches means that mitigation must rely on network controls and configuration changes until an official fix is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 23:00 UTC

Technical details

References

Community reviews

Related threats