Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.2amended

3X-UI Vulnerable to Authenticated Arbitrary File Write via Database Import and Xray Log Path Manipulation

CVE-2026-55477GHSA-jm48-m3rr-9hgg

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/mhsanaei/3x-ui/v2

    Affected
    <= 2.9.4
    Fixed in
    no fixed version recorded

  • Go github.com/mhsanaei/3x-ui

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/mhsanaei/3x-ui/v3

    Affected
    <= 3.3.0
    Fixed in
    3.3.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-55477: 0.61% estimated exploitation activity in the next 30 days; percentile 49.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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). Details The database import functionality trusts attacker-controlled configuration values without sufficient validation. An authenticated administrator can export the SQLite database, modify xrayTemplateConfig.log.access to point to an arbitrary file, and import the modified database back into the panel. The attacker can then inject controlled content into an inbound client's email field. When a connection is processed, Xray writes the attacker-controlled content to the configured access log path. Because the log path is fully attacker-controlled, this behavior results in arbitrary file write as the user running Xray. Depending on the target file and service…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jm48-m3rr-9hgg

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6284

  3. Revision 1 · created ·

    Published from osv record GHSA-jm48-m3rr-9hgg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55477

Advisory: 3X-UI Vulnerable to Authenticated Arbitrary File Write via Database Import and Xray Log Path Manipulation
IDs: CVE-2026-55477, GHSA-jm48-m3rr-9hgg
Record: https://patchnext.com/advisories/cve-2026-55477 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/mhsanaei/3x-ui/v3 3.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/mhsanaei/3x-ui/v2: affected <= 2.9.4
- Go github.com/mhsanaei/3x-ui: affected every version
- Go github.com/mhsanaei/3x-ui/v3: affected <= 3.3.0; fixed in 3.3.1

## Suggested inspection (read-only)
- Go github.com/mhsanaei/3x-ui/v2: check the installed version with your package manager.
- Go github.com/mhsanaei/3x-ui: check the installed version with your package manager.
- Go github.com/mhsanaei/3x-ui/v3: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/mhsanaei/3x-ui/v2, github.com/mhsanaei/3x-ui, github.com/mhsanaei/3x-ui/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jm48-m3rr-9hgg (OSV record GHSA-jm48-m3rr-9hgg lists affected ranges: Go github.com/mhsanaei/3x-ui/v3 >=0 =0 <=2.9.4)
- Verified: https://osv.dev/vulnerability/GO-2026-6284 (OSV record GO-2026-6284 lists affected ranges: Go github.com/mhsanaei/3x-ui >=0; Go github.com/mhsanaei/3x-ui/v2 >=0; Go github.com/mhsanaei/3x-ui/v3 >=0 <3.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-jm48-m3rr-9hgg (GitHub-reviewed advisory GHSA-jm48-m3rr-9hgg lists affected ranges: Go github.com/mhsanaei/3x-ui/v3 >=0 =0 <=2.9.4)

Commands are suggestions: review each one before running it.

Loading voting…