GPU VulnDB

Database/Firmware, BMC & network fabric

Junos OS: reachable assertion in the TWAMP client lets one TCP packet kill rmopd

CVSS 9.2CVE-2026-102070Firmware, BMC & network fabriccurated

Impact

A specific TCP packet to a Junos device running the TWAMP client trips an assertion and takes down rmopd, the daemon behind remote operations and performance measurement. The forwarding plane survives, but the device loses the active measurement that operators use to see latency and loss across the fabric - exactly the telemetry a GPU cluster relies on to notice a sick link before a training job stalls. Repeated packets keep the daemon down. No authentication is needed.

Who can reach it

Network, unauthenticated. Any host that can open a TCP connection to the TWAMP client on the device; in practice whoever can reach the measurement endpoints, which on many fabrics is the management VLAN or a peering segment.

What to do

Upgrade to a fixed Junos release per Juniper advisory JSA112188 - the record does not list fixed versions, so check the advisory against your train. The upgrade is a device reboot. As an interim measure, disable the TWAMP client where it is not in use and filter TWAMP reachability to the measurement collectors.

References

Related entries

All Firmware, BMC & network fabric entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.