CVE Intelligence
Medium

CVE-2026-57029 — Junos OS Evolved: QFX Series: When sFlow collector reachability changes evo-pfemand process can crash

A Missing Synchronization vulnerability in the flow collector handler of Juniper Networks Junos OS Evolved on QFX Series allows an adjacent, unauthenticated attacker to cause a Denial-of-Service (DoS). When the reachability of an sFlow collector changes, the corresponding next-hop entry is updated. If this update occurs simultaneously with the sFlow thread accessing the next-hop data (which is outside the attackers control), it causes the evo-pfemand process to crash, impacting all traffic forwarding until the automatic process restart has completed. This issue affects Junos OS Evolved on QFX Series: * all 23.2 versions,  * 23.4 versions before 23.4R2-S7-EVO, * 24.2 versions before 24.2R2-S5-EVO, * 24.4 versions before 24.4R2-S3-EVO, * 25.2 versions before 25.2R2-EVO.

Published Jul 9, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: juniper

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.19%
ahead of 8% of scored CVEs · Oct 15, 2026
Affects
Juniper Networks
Junos Os Evolved
CVSS base
5.3
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Juniper Networks Junos Os Evolved).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Juniper Networks Junos Os Evolved version 24.4-r2-s2version 24.2-r2-s3version 24.2-r2-s4version 24.4version 24.4-r1version 24.4-r1-s2version 24.4-r1-s3version 24.4-r2
and 23 more version 24.4-r2-s1version 24.2-r2-s2version 25.2version 25.2-r1version 25.2-r1-s1version 25.2-r1-s2version 23.4-r2-s4version 23.4version 23.4-r1version 23.4-r1-s1version 23.4-r1-s2version 23.4-r2version 23.4-r2-s1version 23.4-r2-s2version 23.4-r2-s3version 23.2version 23.4-r2-s5version 23.4-r2-s6version 24.2version 24.2-r1version 24.2-r1-s2version 24.2-r2version 24.2-r2-s1
Vulnerable NIST National Vulnerability Database
Juniper Networks Junos Os Evolved < 23.4R2-S7-EVO≥ 24.2 and < 24.2R2-S5-EVO≥ 24.4 and < 24.4R2-S3-EVO≥ 25.2 and < 25.2R2-EVO Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Adjacent
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.0 CVSS 4.0 Medium — — sirt@juniper.net via NIST National Vulnerability Database
6.0 CVSS 4.0 Medium — — juniper via CVE Program (cve.org) e CISA ADP
5.3 CVSS 3.1 Medium 1.6 3.6 sirt@juniper.net via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — juniper via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: sirt@juniper.net)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-820

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · juniper networks/junos os evolved
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 5.3
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Jul 9, 2026 · juniper

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

Elsewhere on this site

Juniper Networks
every CVE for this vendor
CWE-820
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2026-101982 Junos OS and Junos OS Evolved: A EVPN peer causes an rpd crash or root-level compromise when EVPN-VPWS is used 1d
  • Critical CVE-2026-101983 Junos OS and Junos OS Evolved: An attacker causes remote code execution when J-Web virtual-domain is configured 1d
  • High CVE-2026-101976 Junos OS and Junos OS Evolved: In a non-4byte-AS scenario a specific BGP update causes an rpd crash 1d
  • Medium CVE-2026-101964 Junos OS and Junos OS Evolved: An attacker can cause an rpd crash via a crafted LDP message 1d
  • High CVE-2026-101979 Junos OS and Junos OS Evolved: A network attacker causes root-level code execution or denial of service when SNMP and AAA are enabled 1d
  • Medium CVE-2026-101972 Junos OS and Junos OS Evolved: Malformed OSPF packets causes routing disruption when OSPF is enabled 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-57029 is "Junos OS Evolved: QFX Series: When sFlow collector reachability changes evo-pfemand process can crash", rated Medium. It affects Junos Os Evolved (Juniper Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.