CVE-2026-55477: Authenticated Arbitrary File Write via Database Import and Xray Log Path Manipulation
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-06-25).
Weakness: CWE-73: External Control of File Name or Path
How it can be exploited
Exploitable over the network with low attack complexity needing high privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 9 references on Exploit Observer
Live scores
- EPSS
- 0.006
low predicted chance of attack - VEDAS
- 0.988
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| MHSanaei 3x-ui | version < 3.3.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-55477 3X-UI - Arbitrary File Write via crafted Xray config database import. Add them to your Suricata rule set and reload.
Show the rules
# CVE-2026-55477 - 3X-UI (< 3.3.1) arbitrary file write to RCE. An authenticated administrator
# abuses the database import functionality to set Xray configuration log.access/log.error to an
# attacker-chosen path, causing Xray to write files anywhere on the host (root when Xray runs as
# root). The fix confines those log paths to the panel log folder. The wholesale DB import is the
# named exploitation vector; this matches the import request (POST /panel/api/server/importDB).
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-55477 3X-UI - Arbitrary File Write via crafted Xray config database import"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"server/importDB"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-55477; reference:url,https://www.exploit.observer/?keyword=CVE-2026-55477&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=3x-ui&match=exact; sid:1100802; rev:1;)
CVE-2026-55477.rules on GitHub
References
Other references
- https://github.com/MHSanaei/3x-ui/security/advisories/GHSA-jm48-m3rr-9hgg (x_refsource_CONFIRM)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
