GPU VulnDB

Database/Firmware, BMC & network fabric

Junos rpd: flow-spec update selected for re-advertisement overflows a stack buffer, up to routing-engine compromise

CVSS 9.3CVE-2026-101990Firmware, BMC & network fabric+1 more CVEscurated

Impact

A BGP flow-spec update that the device selects for re-advertisement overflows a stack buffer in the routing daemon, crashing rpd on Junos OS Evolved and allowing routing-engine code execution on Junos OS. Juniper split this flow-spec re-advertisement overflow across two ids in the same advisory (CVE-2026-101990 and CVE-2026-102178, the latter conditioned on BGP update-threading); same component, same class of flaw, same fix, so they are recorded as one. Compromise of the routing engine on a fabric router is the worst case here - the attacker owns route selection for the traffic the cluster depends on, and a route-reflector or border router is not a device you can fail over cheaply.

Who can reach it

A configured BGP flow-spec peer, i.e. a neighbour the device already accepts flow-spec routes from. No authentication beyond an established BGP session. CVE-2026-102178 additionally requires BGP update-threading to be enabled.

What to do

Upgrade Junos OS / Junos OS Evolved to a fixed release from Juniper JSA112187. This is a reboot per device; on route reflectors and border routers plan for the control-plane outage, not just the data-plane one. If flow-spec is not required, removing the flow-spec address family from those sessions, or disabling flow-spec re-advertisement, removes the trigger without an upgrade.

Also covers 1 CVE

The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.

CVE-2026-102178

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.