dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-26291

HIGH · 8.7 CVSS v4.0 Published 2025-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
An Unauthenticated Arbitrary File Read vulnerability affects the Agent when installed on a system. The parameter filename does not validate the path thus allowing users to read arbitrary files. As the application runs with the highest privileges (root/NT_AUTHORITY SYSTEM) by default attackers are able to obtain sensitive information. This issue affects Avid NEXIS E-series: before 2025.5.1; Avid NEXIS F-series: before 2025.5.1; Avid NEXIS PRO+: before 2025.5.1; System Director Appliance (SDA+): before 2025.5.1.

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

Unauthenticated arbitrary file read vulnerability in Avid NEXIS Agent. The filename parameter lacks path validation, allowing attackers to specify any file path on the system. Since the agent runs with root/SYSTEM privileges by default, attackers can read sensitive system files, configuration files, and credentials.

MitigationUpgrade to Avid NEXIS version 2025.5.1 or later for all affected products (E-series, F-series, PRO+, SDA+). Apply network segmentation and monitor for suspicious file access requests as interim controls.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:X/R:X/V:X/RE:X/U:X

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. Verify Avid NEXIS Agent is installed
    Check for the Avid NEXIS Agent service or process on the system. On Linux, look for services related to 'nexis' or 'avid'. On Windows, check Services.msc for 'Avid NEXIS' or similar service names.
    Affected if The Avid NEXIS Agent service or process is found running on the system.
  2. Determine installed Avid NEXIS version
    Locate the Avid NEXIS installation directory and check for version information. Common locations include /opt/avid/nexis or C:\Program Files\Avid\NEXIS. Look for version files, about dialogs, or use any available version command. Compare your version to 2025.5.1.
    Affected if The installed version is lower than 2025.5.1.
  3. Identify if NEXIS Agent web service is exposed
    Check for listening network services on common web ports (80, 443, 8080, 8443) that may be associated with Avid NEXIS Agent. Use netstat or ss to list listening ports, then identify which process owns them.
    Affected if The Avid NEXIS Agent web service is listening on a network port accessible to attackers.
  4. Verify service privilege level
    Check the user context the Avid NEXIS Agent service runs under. On Windows, use Services.msc or 'sc qc' to check the service configuration. On Linux, check the service startup configuration or process ownership.
    Affected if The service runs with root, SYSTEM, or elevated administrator privileges.

The environment is affected if Avid NEXIS Agent is running with elevated privileges and the version is below 2025.5.1, particularly if the web interface is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Avid NEXIS version 2025.5.1 or later for all affected products (E-series, F-series, PRO+, SDA+). Apply network segmentation and monitor for suspicious file access requests as interim controls.

Recommended fix High confidence

Avid NEXIS 2025.5.1 (or later) for E-series, F-series, PRO+, and System Director Appliance (SDA+)

  1. 1. Identify the Avid NEXIS product model (E-series, F-series, PRO+, or SDA+) currently deployed
  2. 2. Backup all current configuration and data according to Avid best practices
  3. 3. Obtain the Avid NEXIS version 2025.5.1 or later from Avid's official support portal (resources.avid.com)
  4. 4. Follow Avid's documented upgrade procedure for the specific appliance model, ensuring the upgrade is performed during a planned maintenance window
  5. 5. After upgrade, verify the Agent component is updated and the arbitrary file read vulnerability is remediated by confirming the filename parameter now properly validates paths
  6. 6. Test that legitimate file access functionality still works as expected

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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