CVE-2026-102178: Junos OS and Junos OS Evolved: When BGP update-threading is enabled a specifically malformed flowspec NLRI causes routing-engine compromise

Published Oct 14, 2026
·
Updated

A Stack-based Buffer Overflow vulnerability in the BGP routing daemon of Juniper Networks Junos OS and Junos OS Evolved allows a configured BGP flowspec peer to cause routing-engine compromise or a routing-daemon denial of service via flowspec route re-advertisement when BGP update-threading is enabled.

Affected Software

2 affected components
Juniper Networks Junos OS
Juniper Networks Junos OS Evolved

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 23.2R2-S7.7-EVO
  2. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 23.4R2-S8.11-EVO
  3. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 24.2R2-S5.6-EVO
  4. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 24.4R2-S5-EVO
  5. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 25.2R2-S2-EVO
  6. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 25.2X100-D35-EVO
  7. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 25.4R1-S3-EVO
  8. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 25.4R2-EVO
  9. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 25.4X300-D40-EVO
  10. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 26.2R1-S2-EVO
  11. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 26.2R2-EVO
  12. Upgrade

    Upgrade Juniper Junos OS Evolved to a version that resolves this vulnerability.

    Fixed in 26.4R1-EVO
  13. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 23.2R2-S7.7
  14. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 23.4R2-S8.13
  15. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 24.2R2-S5.5
  16. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 24.4R2-S5
  17. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 25.2R2-S2
  18. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 25.4R1-S3
  19. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 25.4R2
  20. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 26.2R1-S2
  21. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 26.2R2
  22. Upgrade

    Upgrade Juniper Junos OS to a version that resolves this vulnerability.

    Fixed in 26.4R1

Event History

Oct 14, 2026
CVE Published
via MITRE·04:57 PM
Data Sourced
via MITRE·04:57 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to exploitation?

Affected deployments must use Junos OS or Junos OS Evolved, have BGP update-threading enabled, and have a configured BGP flowspec peer. The vulnerable processing occurs when flowspec routes are re-advertised.

2

What does an attacker need to exploit this issue?

An attacker needs to be a configured BGP flowspec peer capable of sending a specifically malformed flowspec NLRI. No separate authentication bypass or user interaction is described.

3

What is the potential impact of successful exploitation?

Successful exploitation can compromise the routing engine or cause a denial of service in the routing daemon. The stated impact includes high confidentiality, integrity, and availability effects.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203