PatchSiren cyber security CVE debrief
CVE-2026-102070 Juniper Networks CVE debrief
A remote TWAMP peer causes rmopd service disruption when TWAMP-Control is used in Juniper Networks Junos OS, allowing an unauthenticated network-based attacker to cause service disruption via a specific TCP packet. This vulnerability, identified as CVE-2026-102070, affects the Two-Way Active Measurement Protocol (TWAMP) client and requires verification and patching of affected Junos OS versions to prevent potential service disruptions. Network administrators and security teams should assess exposure and prioritize patching, verifying affected versions and restricting TWAMP-Control access to prevent potential exploitation.
- Vendor
- Juniper Networks
- Product
- Junos OS
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-14
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-14
- Advisory updated
- 2026-10-14
Who should care
Network administrators and security teams responsible for Juniper Networks Junos OS deployments should assess exposure and prioritize patching.
Why it matters
CVE-2026-102070 allows remote service disruption in Juniper Networks Junos OS, requiring verification and patching of affected versions.
- Verify and patch affected Junos OS versions to prevent service disruptions
- Restrict TWAMP-Control access to prevent potential exploitation
- Monitor rmopd service for potential disruptions
Technical summary
A Reachable Assertion vulnerability in the Two-Way Active Measurement Protocol (TWAMP) client of Juniper Networks Junos OS allows an unauthenticated network-based attacker to cause rmopd service disruption via a specific TCP packet. The vulnerability affects the TWAMP client and can be exploited through a specific TCP packet, requiring verification and patching of affected Junos OS versions to prevent service disruptions. The CVE record and source item provide details on the vulnerability, but additional information from vendor advisories and source references may
Defensive priority
Network administrators and security teams should prioritize verifying and patching affected Junos OS versions to prevent potential service disruptions.
Recommended defensive actions
- Verify and apply Juniper Networks' official patches for affected Junos OS versions
- Review and update network configurations to restrict TWAMP-Control access
- Monitor rmopd service for potential disruptions
Evidence notes
The CVE record and source item provide details on the vulnerability, but limited information is available on potential exploitation or victim impact. Evidence from the CVE Program record and NIST NVD detail page confirms the vulnerability in Juniper Networks Junos OS. Defenders should verify affected Junos OS versions, review network configurations, and monitor rmopd service for potential disruptions. Additional information from vendor advisories and source references may be necessary.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-102070 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-102070
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-102070 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-102070
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Junos OS: A remote TWAMP peer causes rmopd service disruption when TWAMP-Control is used
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/102xxx/CVE-2026-102070.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://supportportal.juniper.net/JSA112188
Supplemental source - vendor-advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.