HIGH 7.5

CVE-2026-9776: ATEN Unizon Directory Traversal Information Disclosure Vulnerability

ATEN Unizon contains a directory traversal flaw that allows unauthenticated attackers to read sensitive files from the system. The vulnerability exists in a file-handling function that doesn't properly validate user-supplied file paths before accessing them. An attacker can exploit this over the network to retrieve files with SYSTEM-level privileges, potentially exposing passwords, configuration data, or other confidential information stored on the affected device.

Source data · NVD / CISA · public domain

CVSS
3.0 · 7.5 HIGH · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-22
Affected products
1 configuration(s)
Published / Modified
2026-06-24 / 2026-06-27

NVD description (verbatim)

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.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-9776 is a path traversal vulnerability affecting ATEN Unizon's writeFileToHttpServletResponse method. The flaw stems from insufficient input validation on a user-controlled path parameter used in file I/O operations (CWE-22). By crafting requests with directory traversal sequences (e.g., '../'), an unauthenticated remote attacker can bypass intended access controls and read arbitrary files from the host filesystem with SYSTEM-level context. The vulnerability requires no authentication, no user interaction, and operates over the network with low attack complexity.

Business impact

Exploitation enables unauthorized disclosure of sensitive operational and configuration data, including credentials, API keys, database connection strings, and proprietary documentation. For organizations using ATEN Unizon in production environments—particularly in IT management, KVM switching, or remote access scenarios—this vulnerability directly threatens confidentiality and can serve as a reconnaissance vector for follow-on attacks. The SYSTEM context elevation amplifies the risk by granting access to protected OS-level files. Breach of confidential data may trigger regulatory compliance violations (GDPR, HIPAA, PCI-DSS) depending on data classification and jurisdiction.

Affected systems

ATEN Unizon installations are impacted. Organizations running this product—commonly deployed in data centers, server rooms, and IT operations environments—should inventory all instances. The unauthenticated nature of the attack means internet-exposed or insufficiently segmented deployments face immediate risk. Verify specific affected versions against the ATEN security advisory, as patch availability may vary by release line.

Exploitability

Exploitability is straightforward and high-risk. No authentication is required; attackers need only craft a malicious HTTP request with a traversal payload. The attack surface is network-wide, and the low complexity means minimal technical skill is required to execute. The absence of CISA KEV listing does not diminish practical exploitability—active exploitation in the wild is possible immediately upon public disclosure. Organizations should assume adversaries will attempt exploitation rapidly.

Remediation

Apply the security patch from ATEN when available. Verify patch version numbers and deployment procedures directly from the official ATEN security advisory. Until patches are available or deployed, implement compensating controls: restrict network access to Unizon administrative interfaces using firewall rules and VPN/bastion host segmentation, disable the service if not actively required, and monitor for suspicious file-access patterns. Ensure strong network isolation from untrusted networks.

Patch guidance

Contact ATEN support or consult the official security advisory for verified patch version numbers and deployment instructions. Test patches in a non-production environment before widespread rollout to ensure compatibility with your IT infrastructure. Prioritize patching of internet-exposed or DMZ-resident instances first. Document patch application for compliance and incident response records.

Detection guidance

Monitor HTTP request logs for directory traversal patterns targeting the writeFileToHttpServletResponse endpoint, including sequences like '../', '..\', URL-encoded variants (%2e%2e), and absolute path attempts. Alert on 200 responses (successful file reads) from unexpected file paths. Implement network-based intrusion detection rules to flag traversal attempts. Review authentication logs for any unauthenticated access to administrative functions. Forensic analysis should examine system access logs and file-access events for evidence of unauthorized file reads under SYSTEM context.

Why prioritize this

This vulnerability merits immediate attention due to the combination of unauthenticated remote exploitability, high CVSS score (7.5), and direct impact on information confidentiality in a system context. The absence of authentication requirements and low attack complexity make this accessible to a broad threat actor population. Organizations should prioritize patching or isolation of Unizon instances within their critical asset inventory, particularly those managing sensitive infrastructure or storing confidential operational data.

Risk score, explained

The CVSS 3.0 score of 7.5 (HIGH) reflects an unauthenticated network attack (AV:N, AC:L, PR:N, UI:N) with no impact on integrity or availability but full compromise of confidentiality (C:H, I:N, A:N). The lack of user interaction and system-scope elevation justify the high severity designation, though the absence of data manipulation or service disruption prevents a critical rating. In a defense-in-depth context, internal network segmentation may lower practical risk; however, remote exploitability from the internet poses a direct threat.

Frequently asked questions

Is this vulnerability being actively exploited in the wild?

There is no current CISA KEV listing for this CVE, indicating no confirmed active exploitation at the time of publication. However, directory traversal flaws are well-understood attack vectors with readily available exploitation techniques. Organizations should assume exploitation attempts will begin rapidly after public disclosure and patch availability.

Does the attacker need credentials to exploit this?

No. The vulnerability is unauthenticated, meaning any remote attacker can attempt exploitation without valid user credentials or administrator access. This significantly expands the threat actor population with the ability to attempt attacks.

What types of data are at risk?

Any files readable by the SYSTEM user context are at risk, including Windows system files, application configuration files, credentials stored in plaintext or weakly encrypted formats, database connection strings, SSL certificates, and logs containing sensitive information. Organizations should review what sensitive data resides on affected Unizon systems.

Can network segmentation reduce the risk of this vulnerability?

Yes. Restricting network access to Unizon administrative interfaces via firewall rules, placing the device behind a VPN or bastion host, and isolating it from untrusted networks significantly reduces exploitability. However, segmentation is a temporary mitigation and does not replace patching.

This analysis is provided for informational and defensive purposes. No exploit code or step-by-step weaponization instructions are included. Patch version numbers and specific remediation procedures must be verified against official ATEN security advisories. Organizations should conduct internal risk assessments based on their deployment context, network topology, and data sensitivity. Consult with ATEN support and internal security teams before implementing any mitigation or patch strategy. This document does not constitute legal, compliance, or vendor-specific technical advice. Source: NVD (public-domain), retrieved 2026-08-02. Analysis generated by SEC.co (claude-haiku-4-5).