dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2025-59969

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in the advanced forwarding toolkit (evo-aftmand/evo-pfemand) of Juniper Networks Junos OS Evolved on PTX Series or QFX5000 Series allows an unauthenticated, adjacent attacker to cause a Denial of Service (DoS).An attacker sending crafted multicast packets will cause line cards running evo-aftmand/evo-pfemand to crash and restart or non-line card devices to crash and restart. Continued receipt and processing of these packets will sustain the Denial of Service (DoS) condition. This issue affects Junos OS Evolved PTX Series: * All versions before 22.4R3-S8-EVO, * from 23.2 before 23.2R2-S5-EVO, * from 23.4 before 23.4R2-EVO, * from 24.2 before 24.2R2-EVO, * from 24.4 before 24.4R2-EVO. This issue affects Junos OS Evolved on QFX5000 Series: * 22.2-EVO version before 22.2R3-S7-EVO, * 22.4-EVO version before 22.4R3-S7-EVO, * 23.2-EVO versions before 23.2R2-S4-EVO, * 23.4-EVO versions before 23.4R2-S5-EVO, * 24.2-EVO versions before 24.2R2-S1-EVO, * 24.4-EVO versions before 24.4R1-S3-EVO, 24.4R2-EVO. This issue does not affect Junos OS Evolved on QFX5000 Series versions before: 21.2R2-S1-EVO, 21.2R3-EVO, 21.3R2-EVO, 21.4R1-EVO, and 22.1R1-EVO.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A classic buffer overflow vulnerability exists in the advanced forwarding toolkit (evo-aftmand/evo-pfemand) of Juniper Networks Junos OS Evolved on PTX Series and QFX5000 Series. An unauthenticated adjacent attacker can send specially crafted multicast packets that overflow a buffer, causing the affected line cards or devices to crash and restart. Repeated receipt of these packets creates a sustained denial-of-service condition.

MitigationApply the vendor-supplied Junos OS Evolved software updates to reach the fixed versions (22.4R3-S8-EVO, 23.2R2-S5-EVO, 23.4R2-EVO, 24.2R2-EVO, 24.4R2-EVO for PTX Series; 22.2R3-S7-EVO, 22.4R3-S7-EVO, 23.2R2-S4-EVO, 23.4R2-S5-EVO, 24.2R2-S1-EVO, 24.4R1-S3-EVO or 24.4R2-EVO for QFX5000 Series). If patching is not immediately feasible, implement network segmentation and multicast traffic filtering at perimeter devices to limit adjacent attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Junos Os EvolvedOperating system
Affected:< 22.4= 22.4= 23.2= 23.4= 24.2= 24.4= 22.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device series
    Run 'show chassis hardware' or check the device model to confirm it is a PTX Series or QFX5000 Series device. These are the only affected product lines.
    Affected if Device is NOT a PTX or QFX5000 Series device - this CVE does not apply.
  2. Check Junos OS Evolved version
    Run 'show version' or 'show version invoke-on all-routing-engines' to obtain the exact Junos OS Evolved version installed.
    Affected if Version matches any of: < 22.4, = 22.4, = 23.2, = 23.4, = 24.2, = 24.4, or = 22.2 (including any sub-versions within these releases). Compare your exact version string against these.
  3. Verify advanced forwarding toolkit is active
    Run 'show system processes' or check for evo-aftmand or evo-pfemand daemon processes. These processes handle advanced forwarding features and must be running for the vulnerability to be triggerable.
    Affected if The evo-aftmand or evo-pfemand processes are not running or not present on the device.
  4. Check multicast routing configuration
    Run 'show configuration protocols msdp' and 'show configuration protocols pim' or review the multicast routing configuration to see if multicast protocols are enabled.
    Affected if Multicast protocols (PIM, MSDP, IGMP) are NOT configured or disabled - attack requires processing of multicast packets.

The device is affected if it is a PTX or QFX5000 Series running a vulnerable Junos OS Evolved version (22.2, 22.4, 23.2, 23.4, 24.2, or 24.4) with the advanced forwarding toolkit active and multicast processing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.4 or later
Fixed in 22.4
Interim mitigation

Apply the vendor-supplied Junos OS Evolved software updates to reach the fixed versions (22.4R3-S8-EVO, 23.2R2-S5-EVO, 23.4R2-EVO, 24.2R2-EVO, 24.4R2-EVO for PTX Series; 22.2R3-S7-EVO, 22.4R3-S7-EVO, 23.2R2-S4-EVO, 23.4R2-S5-EVO, 24.2R2-S1-EVO, 24.4R1-S3-EVO or 24.4R2-EVO for QFX5000 Series). If patching is not immediately feasible, implement network segmentation and multicast traffic filtering at perimeter devices to limit adjacent attack surface.

Recommended fix High confidence

PTX: 22.4R3-S8-EVO, 23.2R2-S5-EVO, 23.4R2-EVO, 24.2R2-EVO, or 24.4R2-EVO (depending on current branch); QFX5000: 22.2R3-S7-EVO, 22.4R3-S7-EVO, 23.2R2-S4-EVO, 23.4R2-S5-EVO, 24.2R2-S1-EVO, or 24.4R2-EVO (depending on current branch)

  1. 1. Identify the exact Junos OS Evolved version currently running on the device using 'show version detail' command.
  2. 2. Determine if the device is a PTX Series or QFX5000 Series platform using 'show chassis hardware' command.
  3. 3. For PTX Series devices: If running a version before 22.4R3-S8-EVO, upgrade to 22.4R3-S8-EVO or later. If running 23.2.x, upgrade to 23.2R2-S5-EVO or later. If running 23.4.x, upgrade to 23.4R2-EVO or later. If running 24.2.x, upgrade to 24.2R2-EVO or later. If running 24.4.x, upgrade to 24.4R2-EVO or later.
  4. 4. For QFX5000 Series devices: If running 22.2-EVO, upgrade to 22.2R3-S7-EVO or later. If running 22.4-EVO, upgrade to 22.4R3-S7-EVO or later. If running 23.2-EVO, upgrade to 23.2R2-S4-EVO or later. If running 23.4-EVO, upgrade to 23.4R2-S5-EVO or later. If running 24.2-EVO, upgrade to 24.2R2-S1-EVO or later. If running 24.4-EVO, upgrade to 24.4R2-EVO (or 24.4R1-S3-EVO as an alternative).
  5. 5. Download the appropriate upgrade package from the Juniper Networks support portal (https://www.juniper.net/customers/csc/access/).
  6. 6. Upload the upgrade package to the device using 'file copy' or management interface.
  7. 7. Install the upgrade using 'request system software add <package-name>' command with appropriate options (e.g., 'reboot' flag).
  8. 8. After reboot, verify the new version is installed using 'show version detail' command.
Caveat Standard Junos OS Evolved upgrade considerations apply - review Junos Evolved upgrade documentation for specific migration steps and compatibility requirements; plan maintenance window as upgrade requires reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59969 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data