OS Command InjectionWeakness · CWE-78

CVE-2025-0110

HIGH · 8.6 CVSS v4.0 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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 command injection vulnerability in the Palo Alto Networks PAN-OS OpenConfig plugin enables an authenticated administrator with the ability to make gNMI requests to the PAN-OS management web interface to bypass system restrictions and run arbitrary commands. The commands are run as the “__openconfig” user (which has the Device Administrator role) on the firewall. You can greatly reduce the risk of this issue by restricting access to the management web interface to only trusted internal IP addresses according to our recommended best practices deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 .

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 command injection vulnerability exists in the PAN-OS OpenConfig plugin's gNMI interface. An authenticated administrator with gNMI request capabilities can bypass system restrictions and execute arbitrary commands as the '__openconfig' user, which holds Device Administrator privileges on the firewall.

MitigationRestrict access to the PAN-OS management web interface to only trusted internal IP addresses per Palo Alto best practices; consider disabling the OpenConfig plugin if not required.

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

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
Authentication
None
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:M/U:Amber

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. Confirm PAN-OS is in use
    Check the system type: look for PAN-OS-specific processes, web interface, or run 'show system info' in the CLI to identify the OS
    Affected if The target system is running PAN-OS firmware
  2. Verify OpenConfig plugin is installed
    In the PAN-OS web interface, go to Device > OpenConfig, or run 'show plugins package' in the CLI to list installed plugins
    Affected if The OpenConfig plugin is installed and loaded
  3. Confirm gNMI service is enabled
    In the PAN-OS web interface under Device > OpenConfig > gNMI, or run 'show system services gNMI' in the CLI to check service status
    Affected if gNMI service is enabled and accepting requests
  4. Check administrator gNMI permissions
    In the PAN-OS web interface, review admin role assignments under Device > Administrators; look for users with gNMI request capabilities
    Affected if Any admin账户拥有gNMI请求权限(管理员权限)
  5. Review gNMI service access controls
    Check gNMI service listener configuration: verify which IP addresses or interfaces the gNMI service binds to, and whether it is exposed to untrusted networks
    Affected if gNMI service is accessible from untrusted networks or non-management interfaces

The environment is affected if it runs PAN-OS with the OpenConfig plugin installed, gNMI service enabled, and any administrator with gNMI capabilities can access the service from a network path that is not limited to trusted internal IPs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the PAN-OS management web interface to only trusted internal IP addresses per Palo Alto best practices; consider disabling the OpenConfig plugin if not required.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0110 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0110 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