dbcve.org
Ng FirewallApplication · Arista

CVE-2026-25623

MEDIUM · 6.0 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 17.4.1 or later.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable 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
An input validation command execution vulnerability exists in the browser management pipeline of Arista Edge Threat Management - Arista Next Generation Firewall (NGFW). Authenticated administrators can leverage this exposure to obtain underlying terminal script code processing execution permissions.

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 · moderate confidence

This is an input validation vulnerability in the browser management pipeline of Arista Edge Threat Management/NGFW that allows authenticated administrators to execute arbitrary terminal script code. The issue stems from insufficient input sanitization in the management interface, enabling command injection through the browser-based management pipeline.

MitigationImplement strict input validation and sanitization for all user-supplied parameters in the browser management pipeline. Apply proper encoding and use parameterized approaches for any command processing. Restrict administrator privileges where possible and review the command execution flow for additional hardening.

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
Ng FirewallApplication
Affected:< 17.4.1

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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 installed Arista Ng Firewall version
    Access the administrative interface or CLI and retrieve the firmware/software version. In the web UI, this is typically found under System > Maintenance > Updates or similar. From CLI, use commands like 'show version' or check the dashboard for the current build number.
    Affected if The installed version is any release prior to 17.4.1 (e.g., 17.4.0, 17.3.x, earlier releases).
  2. Confirm browser management interface is accessible
    Verify that the web-based management interface is enabled and reachable. This is typically accessible via HTTPS on port 443 or 8443. Check that the management service is running via CLI command such as 'show services' or similar status commands.
    Affected if The web management interface is enabled and exposed, as this is where the vulnerable input pipeline exists.
  3. Verify administrative access controls
    Review the list of configured administrator accounts and their permission levels. Check if any administrator accounts exist with access to the browser management interface. Use 'show admin users' or view user management settings in the web UI.
    Affected if Any administrator account has access to the browser management interface, as authenticated administrators are required to exploit this vulnerability.

You are affected if your Arista Ng Firewall version is below 17.4.1 and the browser management interface is accessible with administrator credentials.

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 17.4.1 or later
Fixed in 17.4.1
Interim mitigation

Implement strict input validation and sanitization for all user-supplied parameters in the browser management pipeline. Apply proper encoding and use parameterized approaches for any command processing. Restrict administrator privileges where possible and review the command execution flow for additional hardening.

Recommended fix Moderate confidence

Ng Firewall version 17.4.1 or later

  1. 1. Back up the current Ng Firewall configuration through the web interface or CLI.
  2. 2. Download the Ng Firewall version 17.4.1 (or latest stable release) from the official Arista support portal at support.arista.com.
  3. 3. Navigate to the System > Firmware or System > Maintenance section in the Ng Firewall management interface.
  4. 4. Upload the firmware image and initiate the upgrade process.
  5. 5. After the system reboots, verify the upgrade was successful by checking the firmware version in the dashboard.
  6. 6. Confirm that the management interface is accessible and the firewall is functioning normally.
Caveat Review Arista release notes for any configuration or behavioral changes between your current version and 17.4.1 before upgrading

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

Fix this in Ng Firewall Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25623 — 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-2026-25623 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