Skip to main content
VulnerabilityPublished Updated

CVE-2025-7616: gmg137 snap7-rs · Memory Corruption

Affects gmg137 snap7-rsSource CVE Database V5

0

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
crates.iogmg137/snap7-rspkg:cargo/gmg137/snap7-rsOther threatsAffected
  • =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

Organizations should prioritize updating or patching the snap7-rs library to a version beyond 1.142.1 once a fix is released by the vendor. In the interim, network segmentation should be enforced to restrict access to systems running snap7-rs, limiting adjacent network exposure. Implement strict access controls and monitoring on OT networks to detect anomalous behavior related to PLC communications. Employ runtime protection and memory safety tools where feasible to detect and prevent memory corruption exploitation attempts. Conduct thorough audits of systems using snap7-rs to identify affected versions and isolate or contain vulnerable instances. Additionally, review and harden synchronization and threading usage in custom integrations with the library to minimize risk. Incident response plans should include scenarios involving PLC communication disruptions. Finally, maintain up-to-date threat intelligence to respond quickly if exploitation attempts emerge.

Description

A vulnerability, which was classified as critical, has been found in gmg137 snap7-rs up to 1.142.1. Affected by this issue is the function pthread_cond_destroy of the component Public API. The manipulation leads to memory corruption. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…