1Panel arbitrary file write vulnerability

Exploitation

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

CVSS

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

EPSS

• CVE-2024-34352: 1.33% estimated exploitation activity in the next 30 days; percentile 71.06 (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.

Summary There are many command injections in the project, and some of them are not well filtered, leading to arbitrary file writes, and ultimately leading to RCEs. We can use the following mirror configuration write symbol to achieve arbitrary file writing PoC Dockerfile echo.sh Build this image like this, upload it to dockerhub, and then 1panel pulls the image to build the container Send the following packet, taking care to change the containerID to the malicious container we constructed Then you can write any customized file to, for example, a ssh key, and generally the application is run with root privileges Or write a timed task to execute any command. Impact The ability to write arbitrary files on the host where the service is deployed can lead to a host takeover

Published by the source

9 May 2024, 15:14 UTC

Last modified by the source

8 Jun 2026, 15:55 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f8ch-w75v-c847

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

# Patch Next advisory brief: CVE-2024-34352

Advisory: 1Panel arbitrary file write vulnerability
IDs: CVE-2024-34352, GHSA-f8ch-w75v-c847
Record: https://patchnext.com/advisories/cve-2024-34352 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/1Panel-dev/1Panel 1.10.3-lts. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/1Panel-dev/1Panel: affected < 1.10.3-lts; fixed in 1.10.3-lts

## Suggested inspection (read-only)
- Go github.com/1Panel-dev/1Panel: 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/1Panel-dev/1Panel.
- 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-f8ch-w75v-c847 (GitHub-reviewed advisory GHSA-f8ch-w75v-c847 lists affected ranges: Go github.com/1Panel-dev/1Panel >=0 <1.10.3-lts)

Commands are suggestions: review each one before running it.