# CVE-2026-9779: ATEN Unizon doCryptoHugeFileToFile Improper Verification of Cryptographic Signature Remote Code Execution Vulnerability

> Remote attackers with authentication can bypass cryptographic signature verification to execute arbitrary code as SYSTEM on ATEN Unizon.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-2h8c-cmrc-4q5c

## What is CVE-2026-9779?

CVE-2026-9779 is a high-severity vulnerability in ATEN Unizon, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ATEN Unizon doCryptoHugeFileToFile Improper Verification of Cryptographic Signature Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of ATEN Unizon. Authentication is required to exploit this vulnerability.

The specific flaw exists within the updateWar method. The issue results from an incorrect implementation of cryptographic signature verification. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-28590.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-9779?

It affects 1 product.


Products: Aten Unizon.

## How do I fix CVE-2026-9779?

No fix has been published for CVE-2026-9779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9779 being exploited?

There is no known exploitation of CVE-2026-9779 in the wild and no public exploit code.

## Other vulnerabilities in ATEN Unizon

- [CVE-2026-9776](https://insights.sbomify.com/CVE-2026-9776/): ATEN Unizon writeFileToHttpServletResponse Directory Traversal Information Disclosure Vulnerability (high 7.5)
- [CVE-2026-9777](https://insights.sbomify.com/CVE-2026-9777/): ATEN Unizon restoreDB Directory Traversal Remote Code Execution Vulnerability (high 7.2)
- [CVE-2026-9778](https://insights.sbomify.com/CVE-2026-9778/): ATEN Unizon ImportDeviceList Directory Traversal Remote Code Execution Vulnerability (high 7.2)
- [CVE-2026-9774](https://insights.sbomify.com/CVE-2026-9774/): ATEN Unizon updateLicense Directory Traversal Arbitrary File Deletion Vulnerability (medium 5.5)
- [CVE-2026-9775](https://insights.sbomify.com/CVE-2026-9775/): ATEN Unizon uploadSSL Directory Traversal Arbitrary File Deletion Vulnerability (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9779 and fix it if it is affected.

What it is: CVE-2026-9779 is a high-severity vulnerability in ATEN Unizon, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9779 in the wild and no public exploit code.

Affected product: ATEN Unizon. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9779/ (Markdown: https://insights.sbomify.com/CVE-2026-9779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9779
- OSV: https://osv.dev/vulnerability/CVE-2026-9779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9779/
Summaries are generated and may contain mistakes; the official description above is the record.