dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-22762

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
Dell Avamar Server and Avamar Virtual Edition, versions prior to 19.10 SP1 with CHF338912, contain an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Security. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to arbitrary file delete.

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

Dell Avamar Server and Avamar Virtual Edition contain a path traversal vulnerability in the Security component that allows a high-privileged attacker with remote access to delete arbitrary files on the system by manipulating file paths outside the intended restricted directory.

MitigationApply vendor patch CHF338912 to upgrade Dell Avamar to version 19.10 SP1 or later, and verify the path traversal protection is functioning correctly.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 the installed Dell Avamar product
    Run 'dmcli -e enq -t get -g System.Product' or check the system inventory for Dell Avamar Server or Avamar Virtual Edition
    Affected if The product is Dell Avamar Server or Avamar Virtual Edition and the version is below 19.10 SP1
  2. Check the Avamar version
    Execute 'dmcli -e enq -t get -g System.Version' or access the Avamar administration console to view the installed version number
    Affected if The installed version is earlier than 19.10.0.10 (19.10 SP1)
  3. Verify remote access configuration
    Review the Avamar security settings under Administration > Access > Remote Access or inspect the /etc/avamar/remoteaccess.conf file if accessible
    Affected if Remote access is enabled for administrative or high-privileged users without additional path traversal restrictions
  4. Confirm Security component availability
    Check if the Security component management interface is accessible via the Avamar GUI (Support > Security) or CLI (avasd management commands)
    Affected if The Security component is enabled and accessible to high-privileged remote users
  5. Inspect path traversal protection controls
    Review security configuration files in /etc/avamar/ or the avtar.config for any path traversal protection settings, or test with a controlled file access attempt using the Security component interface
    Affected if No explicit path traversal protection is configured or the protection mechanism is absent in the Security component settings

A system is affected if it is running Dell Avamar Server or Avamar Virtual Edition with a version below 19.10 SP1, has the Security component enabled, and allows remote high-privileged access without path traversal restrictions in place.

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

Apply vendor patch CHF338912 to upgrade Dell Avamar to version 19.10 SP1 or later, and verify the path traversal protection is functioning correctly.

Recommended fix Moderate confidence

Avamar version 19.10 SP1 with CHF338912

  1. 1. Identify the current installed version of Dell Avamar Server or Avamar Virtual Edition.
  2. 2. If the installed version is prior to 19.10 SP1 with CHF338912, plan for an upgrade.
  3. 3. Contact Dell Support or access the Dell support portal at www.dell.com to obtain the upgrade package for version 19.10 SP1 with CHF338912.
  4. 4. Follow Dell's documented upgrade procedures for Avamar Server or Avamar Virtual Edition.
  5. 5. After upgrade, verify the installation of CHF338912 security hotfix.
  6. 6. Confirm the vulnerability is remediated by verifying the path traversal fix is applied.
Caveat Review Dell upgrade documentation for Avamar to check for any migration requirements, downtime procedures, or compatibility considerations before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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