Zoraxy: Authenticated Path Traversal in Config Import leads to RCE

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-33529: 0.44% estimated exploitation activity in the next 30 days; percentile 38.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Authenticated Path Traversal to RCE via Configuration Import Summary An authenticated path traversal vulnerability in the configuration import endpoint allows an authenticated user to write arbitrary files outside the config directory, which can lead to RCE by creating a plugin. Details The vulnerable endpoint is POST /api/conf/import. The zip entry names sanitization is bypassed by embedding ../ inside a longer sequence so the replacement produces a new ../: Using this endpoint, a new plugin can be written (persistent) and the entrypoint (non-persistent) can be edited to add execution permissions to the plugin. When the database is provided in the import, the program should exit to trigger a container restart (which does not happen because the entrypoint does not monitor the Zoraxy exit code). As a result, the container was manually restarted for the PoC to work. PoC Impact Arbitrary file write leads to RCE by an authenticated user. Given that the Docker socket might be mapped, this…

Published by the source

25 Mar 2026, 20:04 UTC

Last modified by the source

27 Mar 2026, 21:24 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7pq3-326h-f8q9

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

# Patch Next advisory brief: CVE-2026-33529

Advisory: Zoraxy: Authenticated Path Traversal in Config Import leads to RCE
IDs: CVE-2026-33529, GHSA-7pq3-326h-f8q9
Record: https://patchnext.com/advisories/cve-2026-33529 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tobychui/zoraxy 3.3.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tobychui/zoraxy: affected < 3.3.2; fixed in 3.3.2

## Suggested inspection (read-only)
- Go github.com/tobychui/zoraxy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/tobychui/zoraxy.
- 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://github.com/advisories/GHSA-7pq3-326h-f8q9 (GitHub-reviewed advisory GHSA-7pq3-326h-f8q9 lists affected ranges: Go github.com/tobychui/zoraxy >=0 <3.3.2)

Commands are suggestions: review each one before running it.