Skip to content
VulniPulse
Sign in
Medium5.3Juniper Networks

Medium [CVE-2026-57029] 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)

This medium-severity Juniper Networks advisory covers CVE-2026-57029 affecting Junos OS Evolved, Junos OS, Junos.

CVE-2026-57029 Published Jul 9, 2026Updated by vendor Jul 13, 2026
CVE-2026-57029
Affected products & platforms
Juniper NetworksSwitchesJunosJunos OS EvolvedEX / QFX Switches
Open vendor advisory

Android app · Google Play

Monitor future Juniper Networks CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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,
Affected versions
  • 23.2
  • 23.4
  • 24.2
  • 24.4
  • 25.2

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 23.4R2-S7-EVO
  • 24.2R2-S5-EVO
  • 24.4R2-S3-EVO
  • 25.2R2-EVO

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.