CVE-2025-15349VulnerabilityPublished 23 Jan 2026

CVE-2025-15349: Anritsu ShockLine · Race Condition

Affects Anritsu ShockLineSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

7.5High

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

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

CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jan 2026
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-25.

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
AnritsuShockLine	Affected =2025.4.1	Fixed in–

AI-suggested

1. Monitor Anritsu’s official channels closely for the release of security patches addressing CVE-2025-15349 and apply them immediately upon availability. 2. Restrict network access to ShockLine devices by implementing strict network segmentation and firewall rules to limit access only to trusted management hosts. 3. Employ network intrusion detection and prevention systems (IDS/IPS) to monitor for anomalous SCPI command sequences or unusual traffic patterns indicative of exploitation attempts. 4. Conduct regular security audits and configuration reviews of ShockLine deployments to ensure minimal exposure and adherence to security best practices. 5. Where possible, disable or restrict SCPI interfaces on devices not actively used for remote management or testing. 6. Educate network operations teams about the vulnerability and signs of exploitation to enhance detection and response capabilities. 7. Consider deploying endpoint protection solutions capable of detecting unusual process behaviors on devices running ShockLine software. 8. Maintain up-to-date asset inventories to quickly identify and remediate vulnerable devices within the network.

Description

CVE-2025-15349 is a high-severity race condition vulnerability in the SCPI component of Anritsu ShockLine devices, allowing network-adjacent attackers to execute arbitrary code without authentication. The flaw arises from improper synchronization when accessing shared resources, enabling remote code execution in the context of the running process. Exploitation requires no user interaction but has a high attack complexity due to the need for precise timing. Although no known exploits are currently in the wild, the vulnerability impacts confidentiality, integrity, and availability. European organizations using Anritsu ShockLine for network testing and measurement could face significant operational and security risks. Mitigation involves applying vendor patches once available, restricting network access to the device, and monitoring for anomalous activity. Countries with advanced telecommunications infrastructure and heavy use of network testing equipment, such as Germany, France, and the UK, are most likely to be affected. Given the high CVSS score of 7.5, organizations should prioritize addressing this vulnerability promptly.

Impact

For European organizations, the impact of CVE-2025-15349 can be significant, especially for telecommunications providers, network equipment vendors, and enterprises relying on Anritsu ShockLine for network testing and diagnostics. Successful exploitation could lead to unauthorized code execution, allowing attackers to manipulate test results, disrupt network performance monitoring, or pivot into broader network infrastructure. This could compromise the confidentiality of sensitive network data, integrity of diagnostic results, and availability of testing services, potentially delaying incident response and network maintenance. Given the critical role of telecommunications in Europe’s digital economy and infrastructure, such disruptions could have cascading effects on service providers and their customers. Additionally, the lack of authentication requirement increases the risk of exploitation from internal or adjacent network attackers, including malicious insiders or compromised devices within the same network segment. The high attack complexity somewhat limits widespread exploitation but does not eliminate risk in targeted attacks against critical infrastructure.

Summary

CVE-2025-15349 is a race condition vulnerability categorized under CWE-362, affecting the SCPI (Standard Commands for Programmable Instruments) component of Anritsu ShockLine devices, specifically version 2025.4.1. The vulnerability stems from improper synchronization when multiple threads or processes concurrently access and modify shared resources without adequate locking mechanisms. This flaw allows a network-adjacent attacker to exploit timing windows to execute arbitrary code remotely within the context of the ShockLine process. Notably, exploitation does not require authentication or user interaction, though the attack complexity is high due to the need to trigger the race condition precisely. The vulnerability impacts confidentiality, integrity, and availability by enabling arbitrary code execution, potentially leading to full system compromise or disruption of network testing operations. The vulnerability was assigned a CVSS v3.0 score of 7.5, reflecting its high severity with attack vector as adjacent network, high attack complexity, no privileges required, and no user interaction. No public exploits or patches are currently available, but the vulnerability was responsibly disclosed and tracked as ZDI-CAN-27315. The Anritsu ShockLine product is widely used in telecommunications for network performance testing, making this vulnerability particularly critical in environments relying on accurate and secure network diagnostics.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-1200/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jan 2026, 10:10 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats