GPU VulnDB

Database/Firmware, BMC & network fabric

Junos rpd: BGP UPDATE crashes the routing daemon when a policy points at a nonexistent routing table

CVSS 8.7CVE-2026-101939Firmware, BMC & network fabriccurated

Impact

An import policy using then source-based-forwarding next-hop next-table <X> that names a routing table which does not exist leaves rpd open to a NULL dereference when a configured peer sends a BGP UPDATE. The precondition is a configuration mistake an operator can make without any warning at commit time, which means the vulnerable state can exist unnoticed on a production device for a long time. The result is a remotely triggered routing-daemon outage.

Who can reach it

A configured BGP peer sending an UPDATE. Requires an import policy referencing a nonexistent routing table.

What to do

Upgrade Junos OS / Junos OS Evolved to a release from Juniper JSA112187; the upgrade reboots the device. There is also a free fix available now: audit import policies for source-based-forwarding next-table actions and correct any that name a table that does not exist.

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.