CVE-2025-54424

1Panel is a web interface and MCP Server that manages websites, files, containers, databases, and LLMs on a Linux server. In versions 2.0.5 and below, the HTTPS protocol used for communication between the Core and Agent endpoints has incomplete certificate verification during certificate validation, leading to unauthorized interface access. Due to the presence of numerous command execution or high-privilege interfaces in 1Panel, this results in Remote Code Execution (RCE). This is fixed in version 2.0.6. The CVE has been translated from Simplified Chinese using GitHub Copilot.

1Panel is a web interface and MCP Server that manages websites, files, containers, databases, and LLMs on a Linux server. In versions 2.0.5 and below, the HTTPS protocol used for communication between the Core and Agent endpoints has incomplete certificate verification during certificate validation, leading to unauthorized interface access. Due to the presence of numerous command execution or high-privilege interfaces in 1Panel, this results in Remote Code Execution (RCE). This is fixed in version 2.0.6. The CVE has been translated from Simplified Chinese using GitHub Copilot.

Project Address: Project Address 1Panel

Official website: https://www.1panel.cn/

Time: 2025 07 26

Version: 1panel V2.0.5

Vulnerability Summary

• First, we introduce the concepts of 1panel v2 Core and Agent. After the new version is released, 1panel adds the node management function, which allows you to control other hosts by adding nodes.
• The HTTPS protocol used for communication between the Core and Agent sides did not fully verify the authenticity of the certificate during certificate verification, resulting in unauthorized interfaces. The presence of a large number of command execution or high-privilege interfaces in the 1panel led to RCE.

Code audit process

1. First we go to the Agent HTTP routing fileagent/init/router/router.go

2. It was found that the Routersreference function in the function Certificatewas globally checked.agent/middleware/certificate.go

3. The discovery Certificatefunction determines c.Request.TLS.HandshakeCompletewhether certificate communication has been performed

4. Since c.Request.TLS.HandshakeCompletethe true or false judgment is determined by agent/server/server.gothe code Startfunctiontls.RequireAnyClientCert

Note:：Here due to the use of tls.RequireAnyClientCert instead of tls.RequireAndVerifyClientCert，RequireAnyClientCert Only require the client to provide a certificate，Does not verify the issuance of certificates CA，So any self assigned certificate will pass TLS handshake。

5. The subsequent Certificatefunction only verified that the CN field of the certificate was panel_client, without verifying the certificate issuer. Finally, it was discovered that the WebSocket connection could bypass Proxy-ID verification.

6. Process WebSocket interface (based on the above questions, all processes and other sensitive information can be obtained) routing address: /process/ws the request format is as follows

{
  "type": "ps",           // 数据类型: ps(进程), ssh(SSH会话), net(网络连接), wget(下载进度)
  "pid": 123,             // 可选，指定进程ID进行筛选
  "name": "process_name", // 可选，根据进程名筛选
  "username": "user"      // 可选，根据用户名筛选
}

• Terminal SSH WebSocket interface (according to the above problem, any command can be executed) routing address: /hosts/terminal the request format is as follows

{
  "type": "cmd",
  "data": "d2hvYW1pCg=="  // "whoami" 的base64编码，记住不要忘记回车。
}

• Container Terminal WebSocket interface (container execution command interface) routing address:/containers/terminal

• File Download Process WebSocket interface (automatically push download progress information) routing address:/files/wget/process

Attack process

1. First generate a fake certificate openssl req -x509 -newkey rsa:2048 -keyout panel_client.key -out panel_client.crt -days 365 -nodes -subj "/CN=panel_client"

2. Then use the certificate to request verification. If the websocket interface is successfully connected, there is a vulnerability.

1Panel is a web interface and MCP Server that manages websites, files, containers, databases, and LLMs on a Linux server. In versions 2.0.5 and below, the HTTPS protocol used for communication between the Core and Agent endpoints has incomplete certificate verification during certificate validation, leading to unauthorized interface access. Due to the presence of numerous command execution or high-privilege interfaces in 1Panel, this results in Remote Code Execution (RCE). This is fixed in version 2.0.6. The CVE has been translated from Simplified Chinese using GitHub Copilot.

1Panel is a web interface and MCP Server that manages websites, files, containers, databases, and LLMs on a Linux server. In versions 2.0.5 and below, the HTTPS protocol used for communication between the Core and Agent endpoints has incomplete certificate verification during certificate validation, leading to unauthorized interface access. Due to the presence of numerous command execution or high-privilege interfaces in 1Panel, this results in Remote Code Execution (RCE). This is fixed in version 2.0.6. The CVE has been translated from Simplified Chinese using GitHub Copilot.

Project Address: Project Address 1Panel

Official website: https://www.1panel.cn/

Time: 2025 07 26

Version: 1panel V2.0.5

Vulnerability Summary

• First, we introduce the concepts of 1panel v2 Core and Agent. After the new version is released, 1panel adds the node management function, which allows you to control other hosts by adding nodes.
• The HTTPS protocol used for communication between the Core and Agent sides did not fully verify the authenticity of the certificate during certificate verification, resulting in unauthorized interfaces. The presence of a large number of command execution or high-privilege interfaces in the 1panel led to RCE.

Code audit process

1. First we go to the Agent HTTP routing fileagent/init/router/router.go

2. It was found that the Routersreference function in the function Certificatewas globally checked.agent/middleware/certificate.go

3. The discovery Certificatefunction determines c.Request.TLS.HandshakeCompletewhether certificate communication has been performed

4. Since c.Request.TLS.HandshakeCompletethe true or false judgment is determined by agent/server/server.gothe code Startfunctiontls.RequireAnyClientCert

Note:：Here due to the use of tls.RequireAnyClientCert instead of tls.RequireAndVerifyClientCert，RequireAnyClientCert Only require the client to provide a certificate，Does not verify the issuance of certificates CA，So any self assigned certificate will pass TLS handshake。

5. The subsequent Certificatefunction only verified that the CN field of the certificate was panel_client, without verifying the certificate issuer. Finally, it was discovered that the WebSocket connection could bypass Proxy-ID verification.

6. Process WebSocket interface (based on the above questions, all processes and other sensitive information can be obtained) routing address: /process/ws the request format is as follows

{
  "type": "ps",           // 数据类型: ps(进程), ssh(SSH会话), net(网络连接), wget(下载进度)
  "pid": 123,             // 可选，指定进程ID进行筛选
  "name": "process_name", // 可选，根据进程名筛选
  "username": "user"      // 可选，根据用户名筛选
}

• Terminal SSH WebSocket interface (according to the above problem, any command can be executed) routing address: /hosts/terminal the request format is as follows

{
  "type": "cmd",
  "data": "d2hvYW1pCg=="  // "whoami" 的base64编码，记住不要忘记回车。
}

• Container Terminal WebSocket interface (container execution command interface) routing address:/containers/terminal

• File Download Process WebSocket interface (automatically push download progress information) routing address:/files/wget/process

Attack process

1. First generate a fake certificate openssl req -x509 -newkey rsa:2048 -keyout panel_client.key -out panel_client.crt -days 365 -nodes -subj "/CN=panel_client"

2. Then use the certificate to request verification. If the websocket interface is successfully connected, there is a vulnerability.

1Panel agent certificate verification bypass leading to arbitrary command execution in github.com/1Panel-dev/1Panel/core.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/1Panel-dev/1Panel/core before v0.0.0-20250730021757-04b9cbd87a15, from v1.0.0 before v2.0.6.

These are all security issues fixed in the govulncheck-vulndb-0.0.20250811T192933-1.1 package on the GA media of openSUSE Tumbleweed.

This update for govulncheck-vulndb fixes the following issues:

• Update to version 0.0.20250814T182633 2025-08-14T18:26:33Z (jsc#PED-11136)

  Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2025-3765 CVE-2024-44906 GHSA-h4h6-vccr-44h2
  • GO-2025-3829 CVE-2025-54410 GHSA-4vq8-7jfc-9cvp

• Update to version 0.0.20250811T192933 2025-08-11T19:29:33Z (jsc#PED-11136)

  Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2025-3822 CVE-2025-53942 GHSA-9g4j-v8w5-7x42
  • GO-2025-3829 CVE-2025-54410 GHSA-4vq8-7jfc-9cvp
  • GO-2025-3830 CVE-2025-54388 GHSA-x4rx-4gw3-53p4
  • GO-2025-3831 CVE-2025-50738 GHSA-hfcf-79gh-f3jc
  • GO-2025-3832 CVE-2021-21411 GHSA-652x-m2gr-hppm
  • GO-2025-3833 CVE-2025-54576 GHSA-7rh7-c77v-6434
  • GO-2025-3834 CVE-2025-54424 GHSA-8j63-96wh-wh3j
  • GO-2025-3835 CVE-2025-54386 GHSA-q6gg-9f92-r9wg
  • GO-2025-3836 CVE-2025-6037 GHSA-6c5r-4wfc-3mcx
  • GO-2025-3837 CVE-2025-5999 GHSA-6h4p-m86h-hhgh
  • GO-2025-3838 CVE-2025-6000 GHSA-mr4h-qf9j-f665
  • GO-2025-3839 CVE-2025-6011 GHSA-mwgr-84fv-3jh9
  • GO-2025-3840 CVE-2025-6004 GHSA-qgj7-fmq2-6cc4
  • GO-2025-3841 CVE-2025-6014 GHSA-qv3p-fmv3-9hww
  • GO-2025-3842 CVE-2025-6015 GHSA-v6r4-35f9-9rpw
  • GO-2025-3843 CVE-2025-8341 GHSA-3c93-92r7-j934
  • GO-2025-3844 CVE-2025-53534 GHSA-fm3m-jrgm-5ppg
  • GO-2025-3845 CVE-2025-54801 GHSA-qx2q-88mx-vhg7
  • GO-2025-3847 CVE-2025-54799 GHSA-q82r-2j7m-9rv4
  • GO-2025-3848 CVE-2025-6013 GHSA-7rx2-769v-hrwf
  • GO-2025-3851 CVE-2025-44779 GHSA-93jv-pvg8-hf3v
  • GO-2025-3852 CVE-2025-7195 GHSA-856v-8qm2-9wjv
  • GO-2025-3853 CVE-2025-55000 GHSA-f7c3-mhj2-9pvg
  • GO-2025-3854 CVE-2025-54999 GHSA-hh28-h22f-8357
  • GO-2025-3855 CVE-2025-54998 GHSA-j3xv-7fxp-gfhx
  • GO-2025-3856 CVE-2025-55003 GHSA-rxp7-9q75-vj3p
  • GO-2025-3857 CVE-2025-54996 GHSA-vf84-mxrq-crqc
  • GO-2025-3858 CVE-2025-54997 GHSA-xp75-r577-cvhp
  • GO-2025-3859 CVE-2025-55001 GHSA-2q8q-8fgw-9p6p

• Update to version 0.0.20250807T150727 2025-08-07T15:07:27Z (jsc#PED-11136)

  Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2025-3849 CVE-2025-47907