dbcve.org
UnizonApplication · Aten

CVE-2026-9774

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 2.7.264 or later.
See remediation →
71/100
Remediation priority · Elevated
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
ATEN Unizon updateLicense Directory Traversal Arbitrary File Deletion Vulnerability. This vulnerability allows remote attackers to delete arbitrary files on affected installations of ATEN Unizon. Authentication is required to exploit this vulnerability. The specific flaw exists within the updateLicense method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to delete files or create a denial-of-service condition on the system. Was ZDI-CAN-28502.

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

ATEN Unizon contains a directory traversal vulnerability in the updateLicense method. An authenticated attacker can supply a manipulated file path to delete arbitrary files on the system due to insufficient validation of user-supplied paths before file operations.

MitigationApply vendor patches when available. Until then, restrict administrative access to trusted users, implement strict input validation on the updateLicense function, and monitor logs for suspicious file deletion patterns.

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
UnizonApplication
Affected:< 2.7.264

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. Confirm ATEN Unizon installation
    Locate the ATEN Unizon application directory or check for running processes named 'unizon' or similar. Common locations may include /opt/aten/unizon or C:\Program Files\ATEN\Unizon on Windows systems.
    Affected if ATEN Unizon is installed on the system
  2. Check installed version
    Identify the installed version of ATEN Unizon. This may be available in an about page, a version file, or the application UI. Compare the version number against the affected range of versions prior to 2.7.264.
    Affected if The installed version is lower than 2.7.264
  3. Verify updateLicense functionality exposure
    Determine if the updateLicense API endpoint or method is accessible. Check if the web interface or API exposes the updateLicense function used for license file updates.
    Affected if The updateLicense method is exposed and accessible
  4. Review authentication controls
    Examine how authentication is configured for the updateLicense function. Determine whether the method enforces proper authentication and session validation.
    Affected if The updateLicense method can be accessed without valid authentication or with low-privilege authenticated access
  5. Inspect file operation validation
    If logs or configuration are accessible, examine whether input validation is performed on file paths supplied to the updateLicense function. Look for evidence of path sanitization or traversal checks.
    Affected if File paths supplied to updateLicense are not validated for directory traversal sequences such as ../

The environment is affected if ATEN Unizon is installed with a version lower than 2.7.264 and the updateLicense method is accessible to authenticated users without proper path validation.

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

Apply vendor patches when available. Until then, restrict administrative access to trusted users, implement strict input validation on the updateLicense function, and monitor logs for suspicious file deletion patterns.

Recommended fix High confidence

ATEN Unizon 2.7.264 or later

  1. Obtain the ATEN Unizon version 2.7.264 or later from the official ATEN website (www.aten.com) or through your authorized ATEN support channel
  2. Backup the current Unizon installation and configuration data before upgrading
  3. Deploy the upgrade in a non-production environment to verify stability
  4. Apply the upgrade to production systems following standard change management procedures
  5. Verify that the updateLicense function now properly validates paths and rejects directory traversal attempts

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

Fix this in Unizon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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