CVE-2025-15083VulnerabilityPublished 25 Dec 2025Updated 30 Dec 2025

CVE-2025-15083: TOZED ZLT M30s · On-Chip Debug and Test Interface With Improper Access Control

Affects TOZED ZLT M30sSource CVE Database V5

Not known to be exploited · CVSS 1.0 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

1.0Low

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

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

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

Base metrics

Attack Vector: Physical
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
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: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within 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 25 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

Affected software

Product	Affected	Fixed in
TOZED ZLT M30s	Affected =1.0 =1.1 =1.2 =1.3 =1.4 =1.5 =1.6 =1.7 =1.8 =1.9 =1.10 =1.11 =1.12 =1.13 =1.14 =1.15 =1.16 =1.17 =1.18 =1.19 =1.20 =1.21 =1.22 =1.23 =1.24 =1.25 =1.26 =1.27 =1.28 =1.29 =1.30 =1.31 =1.32 =1.33 =1.34 =1.35 =1.36 =1.37 =1.38 =1.39 =1.40 =1.41 =1.42 =1.43 =1.44 =1.45 =1.46 =1.47	Fixed in–

AI-suggested

1. Enforce strict physical security controls to prevent unauthorized access to devices containing TOZED ZLT M30s components, including locked cabinets and surveillance. 2. Disable or restrict access to on-chip debug and test interfaces in production environments where possible, or implement hardware-level protections such as fuses or secure boot mechanisms. 3. Monitor device firmware integrity regularly to detect unauthorized modifications that could indicate exploitation. 4. Segregate networks and limit connectivity of embedded devices to reduce attack surface. 5. Engage with TOZED or suppliers for updates or patches and track vulnerability disclosures for future remediation. 6. Conduct security audits of embedded systems to identify presence of vulnerable devices and plan phased replacement if necessary. 7. Train operational staff on risks associated with physical device access and implement strict access policies. 8. Consider deploying tamper-evident seals or sensors to detect physical intrusion attempts. These measures go beyond generic advice by focusing on physical security and embedded device hardening specific to this vulnerability.

Description

A vulnerability was determined in TOZED ZLT M30s up to 1.47. The affected element is an unknown function of the component UART Interface. Executing manipulation can lead to on-chip debug and test interface with improper access control. The physical device can be targeted for the attack. Attacks of this nature are highly complex. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact is primarily on embedded systems or industrial devices using TOZED ZLT M30s components. Exploitation could allow attackers to manipulate device firmware or extract sensitive information via debug interfaces, potentially compromising device integrity and confidentiality. This could affect critical infrastructure sectors such as manufacturing, energy, and transportation where embedded devices are prevalent. The requirement for physical access limits widespread exploitation but raises concerns for environments with insufficient physical security controls. The lack of vendor patches increases risk over time, especially if attackers develop reliable exploit techniques. Compromise of these devices could lead to operational disruptions, data leakage, or serve as a foothold for further attacks within industrial control systems. However, the low CVSS score and high complexity reduce the likelihood of mass exploitation, making this more relevant for targeted attacks against high-value assets.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Jan 2026, 22:23 UTC

Technical details

References

Community reviews

Related threats