PatchSiren cyber security CVE debrief
CVE-2026-102044 Juniper Networks CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-10-14T16:52:23.433Z and has not been modified since then. This high-severity vulnerability in Juniper Networks Junos OS and Junos OS Evolved can cause a routing control-plane denial of service when BGP-LS traffic engineering is enabled. Network administrators and security teams should assess exposure and potential impact. The vulnerability allows a configured BGP-LS peer to cause a denial of service via a BGP-LS update.
- 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 managing Junos OS and Junos OS Evolved systems should assess exposure and potential impact.
Why it matters
CVE-2026-102044 is a high-severity vulnerability in Juniper Networks Junos OS and Junos OS Evolved that can cause a routing control-plane denial of service when BGP-LS traffic engineering is enabled. Network administrators and security teams should prioritize verifying exposure, assessing potential impact, and applying mitigation measures.
- Potential routing control-plane denial of service via BGP-LS update.
- Possible disruption to network operations and connectivity.
- Need to verify exposure and assess potential impact on network configurations.
- Priority on applying vendor-provided patches or workarounds to mitigate vulnerability.
Technical summary
A Reachable Assertion vulnerability in the rpd process of Juniper Networks Junos OS and Junos OS Evolved allows a configured BGP-LS peer to cause a denial of service via a BGP-LS update. The vulnerability is triggered when BGP-LS traffic engineering is enabled, and it can lead to a routing control-plane denial of service. This can disrupt network operations and connectivity.
Defensive priority
Network administrators and security teams should prioritize verifying exposure and assessing potential impact.
Recommended defensive actions
- Verify exposure by checking Junos OS and Junos OS Evolved versions against the provided affected versions list.
- Assess potential impact on routing control-plane and BGP-LS traffic engineering configurations.
- Consider applying vendor-provided patches or workarounds to mitigate the vulnerability.
- Monitor network and system logs for potential exploitation attempts.
Evidence notes
The CVE record and source item provide details on a Reachable Assertion vulnerability in Juniper Networks Junos OS and Junos OS Evolved, which allows a configured BGP-LS peer to cause a denial of service via a BGP-LS update.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-102044 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-102044
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-102044 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-102044
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Junos OS and Junos OS Evolved: An attacker causes a routing control-plane denial of service when
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/102xxx/CVE-2026-102044.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://supportportal.juniper.net/JSA112187
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.