dbcve.org
UnraidOperating system

CVE-2026-9772

HIGH · 8.8 CVSS v3.0 Published 2026-06-24
Fix available
A fix is available. Upgrade to 7.3.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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
Unraid Web Server FileUpload Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Unraid. Authentication is required to exploit this vulnerability. The specific flaw exists within FileUpload.php. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the www-data user. Was ZDI-CAN-30116.

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

This is a command injection vulnerability in Unraid's FileUpload.php component. The application fails to properly validate user-supplied input before using it in a system call, allowing authenticated remote attackers to execute arbitrary code as the www-data user.

MitigationApply the vendor patch when available. In the interim, restrict network access to the Unraid web interface to trusted users only and monitor for suspicious activity.

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
UnraidOperating system
Affected:< 7.3.0

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Unraid installation and version
    Check the running Unraid version by accessing the web UI (usually https://<your-unraid-ip>) and looking at the top-right corner of the dashboard for the version number, or run 'cat /etc/unraid-version' on the Unraid server CLI if you have shell access
    Affected if The installed version is less than 7.3.0 (e.g., 7.2.x, 7.1.x, 6.x, etc.)
  2. Locate FileUpload.php
    Check if the file exists on the Unraid server by looking in the web root directory (typically /usr/local/emhttp/plugins/webGui or similar web root paths) for FileUpload.php, or attempt to access it via the web browser at https://<your-unraid-ip>/FileUpload.php
    Affected if FileUpload.php exists and is accessible via the web interface
  3. Verify web authentication is required
    Confirm that accessing the Unraid web interface prompts for login credentials. Try accessing FileUpload.php without authenticating - if it returns a login prompt or redirects to login, authentication is enforced
    Affected if FileUpload.php is accessible without requiring authentication (authentication is not properly enforced)
  4. Check for unauthorized shell execution attempts
    Review web server (nginx/apache) access logs and error logs in /var/log for requests to FileUpload.php containing suspicious patterns like semicolons, pipe symbols, backticks, or command operators (e.g., ';', '|', '`', '$()') in the request parameters
    Affected if There are log entries showing requests to FileUpload.php with command injection payloads

Your Unraid instance is affected if it is running a version below 7.3.0 and FileUpload.php is present and accessible on the web interface.

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

Apply the vendor patch when available. In the interim, restrict network access to the Unraid web interface to trusted users only and monitor for suspicious activity.

Recommended fix Moderate confidence

Unraid 7.3.0 or later

  1. 1. Back up your Unraid configuration and any critical data before proceeding with the update.
  2. 2. Log into the Unraid web interface and navigate to the 'Tools' or 'Settings' section.
  3. 3. Check the current Unraid version under 'Settings' > 'System' > 'OS Version'.
  4. 4. Initiate the update through 'Tools' > 'Update' or by downloading Unraid 7.3.0 from the official Unraid.net downloads page.
  5. 5. Apply the update and allow the system to reboot.
  6. 6. After the system restarts, verify the new version is 7.3.0 or later under 'Settings' > 'System' > 'OS Version'.
Caveat Review Unraid 7.3.0 release notes for any breaking changes before upgrading

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

Fix this in Unraid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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