CVE-2026-57025
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 · uneditedA Return of Pointer Value Outside of Expected Range vulnerability in the fileio library of Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privilged attacker to cause a Denial-of-Service (DoS). On EX Series, QFX Series and MX Series a low-privileged attacker issuing a specific 'show l2-learning' or 'show ethernet-switching' command will cause an l2ald crash which will lead to a temporary service impact for all layer 2 services until the process has automatically restarted. This issue affects EX Series, QFX Series, MX Series: Junos OS: * all versions before 23.2R2-S7, * 23.4 versions before 23.4R2-S7, * 24.2 versions before 24.2R2, * 24.4 versions before 24.4R1-S2. Junos OS Evolved: * all versions before 23.2R2-S7-EVO, * 23.4 versions before 23.4R2-S8-EVO, * 24.2 versions before 24.2R2-EVO, * 24.4 versions before 24.4R1-S3-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 confidenceA Return of Pointer Value Outside of Expected Range vulnerability exists in the fileio library of Juniper Networks Junos OS and Junos OS Evolved. A local, low-privileged attacker can trigger a crash of the l2ald process by issuing specific 'show l2-learning' or 'show ethernet-switching' commands, causing denial of service for all layer 2 services until the process automatically restarts.
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< 23.2= 23.2= 23.4= 24.2= 24.4< 23.2= 23.2= 23.4= 24.2= 24.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Junos OS versionRun 'show version' or 'request system version' to obtain the exact installed version of Junos OS or Junos OS EvolvedAffected if The installed version matches < 23.2, or equals 23.2, 23.4, 24.2, or 24.4 without the vendor patch applied (23.2R2-S7, 23.4R2-S7, 24.2R2, or 24.4R1-S2 and later for Junos OS; 23.2R2-S7-EVO, 23.4R2-S8-EVO, 24.2R2-EVO, or 24.4R1-S3-EVO and later for Junos OS Evolved)
-
Confirm the l2ald process is activeRun 'show system processes' or check process status for l2ald daemonAffected if The l2ald process is running, which is required for the denial of service to occur
-
Verify layer 2 learning features are configuredRun 'show l2-learning interfaces' or 'show ethernet-switching interface' to check if Layer 2 learning or Ethernet switching is enabledAffected if Layer 2 learning or Ethernet switching features are active, as these are required for the vulnerable code path to be exercised
-
Test for crash condition using the trigger commandsExecute 'show l2-learning' and 'show ethernet-switching' commands and observe if the l2ald process crashes or becomes unresponsiveAffected if The commands cause the l2ald process to crash or hang, confirming the vulnerability is present
If the Junos OS/Evolved version is in the affected list (before 23.2R2-S7/23.2R2-S7-EVO, or equal to 23.2/23.4/24.2/24.4 without the corresponding patch) AND layer 2 services are enabled, the environment is vulnerable to denial of service via the specified commands.
Generated from the published advisory. Verify against your own configuration.
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 · scoped23.2
Apply the vendor-supplied patches: Junos OS versions 23.2R2-S7, 23.4R2-S7, 24.2R2, or 24.4R1-S2 and later; Junos OS Evolved versions 23.2R2-S7-EVO, 23.4R2-S8-EVO, 24.2R2-EVO, or 24.4R1-S3-EVO and later.
Junos OS: 23.2R2-S7 / 23.4R2-S7 / 24.2R2 / 24.4R1-S2 or later; Junos OS Evolved: 23.2R2-S7-EVO / 23.4R2-S8-EVO / 24.2R2-EVO / 24.4R1-S3-EVO or later
- 1. Identify the current Junos OS or Junos OS Evolved version installed on the device using 'show version' command
- 2. For Junos OS devices: Upgrade to one of the following fixed versions: 23.2R2-S7, 23.4R2-S7, 24.2R2, or 24.4R1-S2 (or later)
- 3. For Junos OS Evolved devices: Upgrade to one of the following fixed versions: 23.2R2-S7-EVO, 23.4R2-S8-EVO, 24.2R2-EVO, or 24.4R1-S3-EVO (or later)
- 4. After upgrade, verify the l2ald process is running normally using 'show system processes' or equivalent
- 5. Test that 'show l2-learning' and 'show ethernet-switching' commands execute without crashing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57025 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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