CVE-2025-15247VulnerabilityPublished 30 Dec 2025Updated 24 Feb 2026

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

Affects gmg137 snap7-rsSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 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 38% 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 30 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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

AI-suggested

Organizations should immediately inventory their use of snap7-rs libraries and identify affected systems. Given the absence of an official patch, consider implementing network-level protections such as strict firewall rules to limit access to PLC communication ports and isolate affected devices within segmented networks. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to detect exploitation attempts targeting snap7-rs. Monitor network traffic for anomalous download requests to the S7Client::download function. Engage with the snap7-rs community or maintainers to track updates or unofficial patches. Where possible, replace or wrap snap7-rs usage with safer, validated communication libraries. Conduct thorough security testing and code audits on custom integrations involving snap7-rs. Develop incident response plans specific to industrial control system compromises. Finally, maintain up-to-date backups and ensure recovery procedures are tested to mitigate potential denial-of-service impacts.

Description

A vulnerability was identified in gmg137 snap7-rs up to 153d3e8c16decd7271e2a5b2e3da4d6f68589424. Affected by this issue is the function snap7_rs::client::S7Client::download of the file client.rs. Such manipulation leads to heap-based buffer overflow. The attack can be executed remotely. The exploit is publicly available and might be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The heap-based buffer overflow in snap7-rs can lead to remote code execution, denial of service, or memory corruption, which could disrupt industrial control systems relying on Siemens S7 PLC communication. Such disruptions can halt manufacturing processes, cause safety hazards, or lead to data breaches. The lack of authentication and user interaction requirements increases the attack surface, allowing attackers to exploit the vulnerability remotely with minimal effort. Since snap7-rs is used in automation and industrial environments, the impact extends to critical infrastructure sectors such as manufacturing, energy, and transportation. The rolling release model and absence of vendor response complicate timely patching, increasing exposure duration. Public availability of exploit code further elevates risk, potentially enabling threat actors to develop automated attacks. Organizations worldwide using snap7-rs or derivative products may face operational downtime, financial losses, reputational damage, and regulatory consequences if exploited.

Summary

CVE-2025-15247 identifies a heap-based buffer overflow vulnerability in the snap7-rs library, an implementation used to communicate with Siemens S7 PLCs (Programmable Logic Controllers). The vulnerability resides in the download function of the S7Client class within client.rs, where improper handling of input data leads to an overflow condition on the heap memory. This flaw can be triggered remotely without authentication or user interaction, making it accessible to unauthenticated attackers over the network. The overflow could potentially allow attackers to execute arbitrary code, cause denial of service, or corrupt memory, impacting the confidentiality, integrity, and availability of systems using this library. The snap7-rs project follows a rolling release model, which means traditional versioning is replaced by commit hashes, complicating patch management and vulnerability tracking. The vulnerability was responsibly disclosed but remains unpatched as of the publication date. Public exploit code is available, increasing the risk of exploitation. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects network attack vector, low attack complexity, no privileges or user interaction required, and partial impacts on confidentiality, integrity, and availability. This vulnerability is particularly relevant for organizations using snap7-rs in industrial automation, manufacturing, or critical infrastructure environments where Siemens S7 PLCs are deployed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:42 UTC

Technical details

References

Community reviews

Related threats