cve.bz

CVE-2026-57029 juniper junos os evolved: Missing Synchronization

6.0 mediumEPSS 0.2%

Medium (6.0) in juniper junos os evolved. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/RE:M

CVSS 3.1

5.3 medium
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-820 Missing Synchronization
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-57029 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57029?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57029?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-57029 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-57029

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-57029](https://cve.bz/cve/badge/CVE-2026-57029.svg)](https://cve.bz/cve/CVE-2026-57029)

HTML:

<a href="https://cve.bz/cve/CVE-2026-57029"><img src="https://cve.bz/cve/badge/CVE-2026-57029.svg" alt="CVE-2026-57029"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Juniper Networks Junos OS Evolvedbefore 23.4R2-S7-EVO
Juniper Networks Junos OS Evolvedfrom 24.2 before 24.2R2-S5-EVO
Juniper Networks Junos OS Evolvedfrom 24.4 before 24.4R2-S3-EVO
Juniper Networks Junos OS Evolvedfrom 25.2 before 25.2R2-EVO

References

Check your stackJSON