VulnerabilityPublished 2 Dec 2025

CVE-2025-41743: Sprecher Automation SPRECON-E-C · Inadequate Encryption Strength

Affects Sprecher Automation SPRECON-E-CSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.0Medium

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

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 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 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
Sprecher Automation SPRECON-E-C	Affected =1.0	Fixed in–

AI-suggested

Restrict physical and local network access to devices running Sprecher Automation SPRECON-E-C, SPRECON-E-P, and SPRECON-E-T3 products to trusted personnel only.
Implement strict access control policies and monitor local access logs for unauthorized attempts.
Employ network segmentation to isolate industrial control systems from general IT networks, reducing the likelihood of local access by unprivileged users.
Regularly audit and update device firmware and software; apply patches promptly once Sprecher Automation releases fixes addressing this vulnerability.
Use endpoint security solutions capable of detecting anomalous local activities related to firmware or update image extraction.
Educate operational technology (OT) staff about the risks of local access vulnerabilities and enforce security best practices in industrial environments.
Consider additional encryption or obfuscation layers for update images if custom solutions are feasible within the operational context.

Description

Insufficient encryption strength in Sprecher Automation SPRECON-E-C, SPRECON-E-P, and SPRECON-E-T3 allows a local unprivileged attacker to extract data from update images and thus obtain limited information about the architecture and internal processes.

Impact

For European organizations, especially those operating in industrial automation, manufacturing, and critical infrastructure sectors, this vulnerability poses a moderate risk. The exposure of architectural and internal process information could aid attackers in developing targeted attacks, potentially leading to intellectual property theft or facilitating future exploitation of other vulnerabilities. Although the vulnerability does not directly compromise system integrity or availability, the leakage of sensitive design information may weaken the overall security posture. Organizations with on-premises Sprecher Automation devices are at risk if local access controls are insufficient. The impact is more pronounced in environments where physical or local network access is easier to obtain, such as shared industrial sites or facilities with less stringent access controls. The lack of known exploits reduces immediate risk, but the vulnerability should be addressed proactively to prevent escalation.

CWE-326Inadequate Encryption Strength (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
Architecture and Design
Use an encryption scheme that is currently considered to be strong by experts in the field.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.3 (opens in a new tab)
V6.2.7 (opens in a new tab)
V6.2.4 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Brute Force (opens in a new tab)
Protocol Analysis (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

sprecher-automation.com/fileadmin/itSecurity/PDF/SPR-2511043_de.pdf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Dec 2025, 14:34 UTC

WeaknessesCWE-326

Technical details

References

Community reviews

Related threats