Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

aqua · Vulnerability

CVSS 3.1 6.6 MEDIUMEUVD CVSS 3.1 6.6 CVSS 3.1 · [email protected] · Secondary 6.6 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/aquaproj/aqua/v2 2.60.1osv · severity unknownFixed by github.com/aquaproj/aqua/v2 2.60.1KEV status unknown

cve-program · CVE-2026-55569

Published

aqua is a declarative command-line version manager written in Go. Prior to 2.60.1, pkg/unarchive/archives.go in the handler.HandleFile method calls os.Symlink with archives.FileInfo.LinkTarget without verifying that the target remains under the extraction destination. A later regular-file entry at the same archive path is opened with OpenFile using O_CREATE and O_WRONLY, which follows the attacker-planted symlink. A malicious or compromised package archive can therefore write attacker-controlled bytes outside aqua's extraction directory with the privileges of the user running aqua, potentially overwriting shell startup files, tool configuration, or writable executable paths. This issue is fixed in version 2.60.1.

Read the publisher's advisory

euvd · EUVD-2026-67827

Published

aqua is a declarative command-line version manager written in Go. Prior to 2.60.1, pkg/unarchive/archives.go in the handler.HandleFile method calls os.Symlink with archives.FileInfo.LinkTarget without verifying that the target remains under the extraction destination. A later regular-file entry at the same archive path is opened with OpenFile using O_CREATE and O_WRONLY, which follows the attacker-planted symlink. A malicious or compromised package archive can therefore write attacker-controlled bytes outside aqua's extraction directory with the privileges of the user running aqua, potentially overwriting shell startup files, tool configuration, or writable executable paths. This issue is fixed in version 2.60.1.

Read the publisher's advisory

nvd · CVE-2026-55569

Published

aqua is a declarative command-line version manager written in Go. Prior to 2.60.1, pkg/unarchive/archives.go in the handler.HandleFile method calls os.Symlink with archives.FileInfo.LinkTarget without verifying that the target remains under the extraction destination. A later regular-file entry at the same archive path is opened with OpenFile using O_CREATE and O_WRONLY, which follows the attacker-planted symlink. A malicious or compromised package archive can therefore write attacker-controlled bytes outside aqua's extraction directory with the privileges of the user running aqua, potentially overwriting shell startup files, tool configuration, or writable executable paths. This issue is fixed in version 2.60.1.

Read the publisher's advisory

osv · GHSA-mf5c-hw34-4hpp

Published

### Summary `aquaproj/aqua` extracts downloaded tool archives through `pkg/unarchive/archives.go` using `github.com/mholt/archives`. The archive handler creates symlink entries with `os.Symlink(f.LinkTarget, dstPath)` without validating that the symlink target resolves inside the extraction destination. A subsequent regular-file archive entry with the same path is opened with `OpenFile(dstPath, O_CREATE|O_WRONLY)`, which follows the attacker-planted symlink. A malicious or compromised aqua package / release asset can therefore write attacker-controlled bytes outside aqua's extraction directory, with the privileges of the user running aqua. ### Details Affected file: `pkg/unarchive/archives.go` Affected function: `(*handler).HandleFile` The vulnerable logic is the combination of: ```go os.Symlink(f.LinkTarget, dstPath) ``` for symlink entries, followed by: ```go h.fs.OpenFile(dstPath, os.O_CREATE|os.O_WRONLY, f.Mode()) ``` for a later regular file entry at the same archive path. The symlink target is not jailed to the extraction destination, and the later file open follows the symlink. The attached PoC uses a two-entry `tar.gz` archive: 1. symlink `pwn -> <outside target>`; 2. regular file `pwn` containing attacker-controlled bytes. The same `mholt/archives` extraction flow is used for the vulnerable handler and for a negative-control handler using a destination-root jail. ### PoC Attachment: `submission_aqua_archive_symlink_traversal_v2_final.zip` Run: ```bash go run mkarchive.go /tmp/aqua-outside-target go build -o aqua-archive-poc . mkdir -p /tmp/aqua-dest ./aqua-archive-poc vuln /tmp/aqua-dest malicious.tar.gz cat /tmp/aqua-outside-target mkdir -p /tmp/aqua-dest-safe ./aqua-archive-poc safe /tmp/aqua-dest-safe malicious.tar.gz ``` Expected vulnerable result: ```text /tmp/aqua-outside-target contains PWNED_BY_AQUA_SYMLINK_TRAVERSAL ``` Expected safe-control result: ```text The escaping symlink / write is rejected and the outside target is unchanged. ``` ### Impact An attacker who controls an archive that aqua installs can write attacker-controlled content to paths outside the extraction destination, limited by the filesystem permissions of the user running aqua. This can lead to user-level code execution if the overwritten path is later executed or interpreted, for example a shell startup file, a tool configuration file, or a writable PATH entry. This report does not claim privilege escalation beyond the aqua process privileges.

Read the publisher's advisory

osv · GO-2026-6314

Published

Aqua's archive extraction follows attacker-planted symlinks, allowing writes outside the install directory in github.com/aquaproj/aqua

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current