UnizonApplication · Aten

CVE-2026-9776

HIGH · 7.5 CVSS v3.0 Published 2026-06-24
Fix available
A fix is available. Upgrade to 2.7.264 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 writeFileToHttpServletResponse Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of ATEN Unizon. Authentication is not required to exploit this vulnerability. The specific flaw exists within the writeFileToHttpServletResponse 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 disclose information in the context of SYSTEM. Was ZDI-CAN-28505.

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

A directory traversal vulnerability exists in ATEN Unizon's writeFileToHttpServletResponse method due to insufficient validation of user-supplied file paths. Remote attackers can exploit this without authentication to read arbitrary files on the system, potentially exposing sensitive configuration data, credentials, or system files.

MitigationImplement strict path validation and canonicalization in the writeFileToHttpServletResponse method to prevent traversal sequences (../). Until vendor patch is available, restrict network access to the Unizon service.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
    Look for the Unizon service or application on the system. Check for Unizon processes running, or look in common installation directories for the Unizon application files.
    Affected if ATEN Unizon software is present on the system
  2. Determine installed version
    Check the Unizon application for its version number. This is typically visible in the web interface, an about page, or a version file in the installation directory.
    Affected if The version is below 2.7.264
  3. Verify writeFileToHttpServletResponse is exposed
    Identify if the Unizon web service is accessible and check if the file download functionality is enabled. This method is typically exposed through a web endpoint.
    Affected if The Unizon web interface is accessible and the file response method is available
  4. Check network accessibility
    Determine if the Unizon service is exposed to network access. Verify whether it binds to external interfaces or is restricted to localhost only.
    Affected if The Unizon service is reachable from network locations rather than only local access

A system is affected if ATEN Unizon version is below 2.7.264 and the web service with the vulnerable writeFileToHttpServletResponse method is accessible, allowing unauthenticated directory traversal attacks.

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

Implement strict path validation and canonicalization in the writeFileToHttpServletResponse method to prevent traversal sequences (../). Until vendor patch is available, restrict network access to the Unizon service.

Fix this in Unizon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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