Juniper Junos OS Flaw Exposes Networks to Remote Root Code Execution
A critical heap overflow in Juniper’s service-deployment daemon allows unauthenticated attackers to seize full control of network devices.

Key points
- CVE-2026-102175 carries a CVSS score of 9.8, classified as critical by the National Vulnerability Database.
- The flaw affects the sdxd service-deployment daemon in Junos OS and Junos OS Evolved before specific patch versions.
- Attackers can execute code as root or cause denial of service by intercepting SDX or SRC server connections.
Organisations relying on Juniper Networks infrastructure face immediate operational risk from a critical vulnerability in the company’s operating systems. The flaw, tracked as CVE-2026-102175, enables remote, unauthenticated attackers to execute code with root privileges or disrupt services. This exposure stems from a heap-based buffer overflow within the sdxd service-deployment daemon. Network administrators must assess their exposure to this vector immediately.
The risk
The National Vulnerability Database rates CVE-2026-102175 as critical, assigning it a base CVSS score of 9.8. The vulnerability is classified under CWE-122, indicating a heap-based buffer overflow. An attacker who can control or intercept the configured SDX or SRC server connection can exploit this weakness. By sending a crafted frame over the service-deployment TCP connection, the adversary can trigger the overflow. This allows for full remote code execution as root or a denial of service condition.
Who is exposed
Juniper Networks Junos OS versions prior to 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, and 24.4R2-S5 are affected by this vulnerability. Junos OS Evolved is also exposed in versions before 23.2R2-S7.7-EVO, 23.4R2-S8.11-EVO, 24.2R2-S5.6-EVO, and 24.4R2-S5-EVO. As CloudSec Pulse reported on 2026-10-14, Juniper devices have previously faced critical flaws allowing root access, highlighting ongoing security challenges for administrators using these platforms.
Cost and compliance
The source material does not provide specific financial impact data or regulatory compliance implications for CVE-2026-102175. However, the ability for an unauthenticated attacker to achieve root access typically triggers significant incident response costs and potential audit failures. Organisations should review their internal risk frameworks to understand how this exposure aligns with their security obligations. No specific compliance mandates are cited in the NVD record.
What happens next
Managers should verify the versions of Junos OS and Junos OS Evolved running on their network infrastructure immediately. If any device matches the affected version lists provided by the National Vulnerability Database, the organisation is exposed to remote root access. Teams should monitor for unusual traffic on SDX or SRC server connections, as these are the vectors for exploitation. Prioritise patching or isolation of vulnerable systems to mitigate the risk of code execution.
Questions to ask your suppliers
Organisations should ask managed service providers whether they have inventory visibility into all Juniper devices under their care. Determine if the supplier has a process for rapid patch deployment for critical vulnerabilities like this one. Ask which team members are responsible for monitoring service-deployment daemon traffic for anomalies. Ensure that incident response plans include steps for isolating devices with exposed SDX or SRC connections. Verify that your supplier understands the severity of unauthenticated remote root access and has updated their security protocols accordingly.
Background: National Vulnerability Database
The National Vulnerability Database is a centralized repository that standardizes information about software weaknesses. It assigns unique identifiers to each flaw, allowing security tools to automatically detect and assess risks in your systems without manual research.
Read the full guide: National Vulnerability Database Explained: How NVD Works for You
What to do and how to stay safe: Juniper Networks
- Audit your network inventory to identify any devices running affected versions of Junos OS or Junos OS Evolved.
- Monitor TCP connections to SDX and SRC servers for crafted frames or unusual traffic patterns that may indicate exploitation.
- Isolate vulnerable devices from untrusted networks until a vendor-provided update can be applied and verified.
- Review access controls for service-deployment daemons to ensure only authorised connections are permitted.
Step-by-step guide: Vulnerability Prioritization: Fix What Actually Breaks Your Business
General security guidance from the CloudSec Pulse newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-102175?
The National Vulnerability Database assigns a CVSS score of 9.8 to this vulnerability, classifying it as critical.
Which Juniper products are affected by this heap overflow?
Junos OS and Junos OS Evolved versions prior to specific release updates, including 23.2R2, 23.4R2, 24.2R2, and 24.4R2 branches, are affected.
How can an attacker exploit this vulnerability?
An unauthenticated attacker who can control or intercept the SDX or SRC server connection can send a crafted frame to trigger the buffer overflow.



