# CVE-2026-55477: Authenticated Arbitrary File Write via Database Import and Xray Log Path Manipulation

> Authenticated administrators can achieve arbitrary file write and code execution by manipulating Xray log paths via database import.

- **Severity:** High 7.2 (`CVSS:3.1/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:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-jm48-m3rr-9hgg, GO-2026-6284

## What is CVE-2026-55477?

CVE-2026-55477 is a high-severity path traversal vulnerability in MHSanaei 3x-ui, published on 25 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

3X-UI is a web control panel for managing Xray-core servers. Prior to 3.3.1, an authenticated administrator can abuse the database import functionality to achieve arbitrary file write on the host by modifying Xray configuration values stored in the database. This can be leveraged to obtain code execution and persistent access as the user running Xray (including root when Xray is running as root). This vulnerability is fixed in 3.3.1.

Weakness: CWE-73 (External Control of File Name or Path)

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

7 open source packages ship an affected version, including github.com/mhsanaei/3x-ui/v2, github.com/mhsanaei/3x-ui and github.com/mhsanaei/3x-ui/v3.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mhsanaei/3x-ui/v2` | Go | All versions | None |
| `github.com/mhsanaei/3x-ui/v2` | Go | All versions to 2.9.4 | None |
| `github.com/mhsanaei/3x-ui/v2` | Go | All versions to 2.9.4 | None |
| `github.com/mhsanaei/3x-ui` | Go | All versions | None |
| `github.com/mhsanaei/3x-ui/v3` | Go | All versions | 3.3.1 |
| `github.com/mhsanaei/3x-ui/v3` | Go | All versions | 3.3.1 |
| `github.com/mhsanaei/3x-ui/v3` | Go | All versions | 3.3.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-55477 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55477 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55477 is a high-severity path traversal vulnerability in MHSanaei 3x-ui, published on 25 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55477 exists.

Affected packages and fixed versions:
- github.com/mhsanaei/3x-ui/v2 (Go): affected all versions; no fix listed
- github.com/mhsanaei/3x-ui/v2 (Go): affected all versions up to 2.9.4; no fix listed
- github.com/mhsanaei/3x-ui/v2 (Go): affected all versions up to 2.9.4; no fix listed
- github.com/mhsanaei/3x-ui (Go): affected all versions; no fix listed
- github.com/mhsanaei/3x-ui/v3 (Go): affected all versions; fixed in 3.3.1
- github.com/mhsanaei/3x-ui/v3 (Go): affected all versions; fixed in 3.3.1
- github.com/mhsanaei/3x-ui/v3 (Go): affected all versions; fixed in 3.3.1

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-55477/ (Markdown: https://insights.sbomify.com/CVE-2026-55477/index.md)
```

## Sources

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

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