Skip to content

← Actionable
High, CVSS 7.7

RatPanel can perform remote command execution without authorization

CVE-2025-53534GHSA-fm3m-jrgm-5ppg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/tnborg/panel 2.5.6, 0.0.0-20250707071915-4985eb2e1f38), redeploy, then verify what is actually installed.

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.

Affected packages

  • Go github.com/tnborg/panel

    Affected
    >= 2.3.19, < 2.5.6>= 0.0.0-20241111062800-91ecd04c2700, < 0.0.0-20250707071915-4985eb2e1f38
    Fixed in
    0.0.0-20250707071915-4985eb2e1f38, 2.5.6

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-fm3m-jrgm-5ppg lists affected ranges: Go github.com/tnborg/panel >=2.3.19 =0.0.0-20241111062800-91ecd04c2700 <0.0.0-20250707071915-4985eb2e1f38

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-53534: 0.69% estimated exploitation activity in the next 30 days; percentile 52.91 (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 When an attacker obtains the backend login path of RatPanel (including but not limited to weak default paths, brute-force cracking, etc.), they can execute system commands or take over hosts managed by the panel without logging in. In addition to this remote code execution (RCE) vulnerability, the flawed code also leads to unauthorized access. Details In Go, r.URL.Path retrieves the part of the URL that comes after the port and before the query parameters or anchor symbols. For example, in the URL http://localhost:8080/api/ws/ssh?id=1, the retrieved path would be /api/ws/ssh. However, if the request is made to http://localhost:8080//api/ws/ssh?id=1, the parsed r.URL.Path would be //api/ws/ssh. RatPanel uses the CleanPath middleware provided by github.com/go-chi/chi package to clean URLs, The route path inside the chi router will be cleaned to /api/ws/ssh, but this middleware does not process r.URL.Path, so the path is still //api/ws/ssh. In the mustlogin middleware, RatPanel…

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

    Published from ghsa record GHSA-fm3m-jrgm-5ppg

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-2025-53534

Advisory: RatPanel can perform remote command execution without authorization
IDs: CVE-2025-53534, GHSA-fm3m-jrgm-5ppg
Record: https://patchnext.com/advisories/cve-2025-53534 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tnborg/panel 2.5.6, 0.0.0-20250707071915-4985eb2e1f38. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tnborg/panel: affected >= 2.3.19, < 2.5.6; >= 0.0.0-20241111062800-91ecd04c2700, < 0.0.0-20250707071915-4985eb2e1f38; fixed in 0.0.0-20250707071915-4985eb2e1f38, 2.5.6

## Suggested inspection (read-only)
- Go github.com/tnborg/panel: 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/tnborg/panel.
- 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-fm3m-jrgm-5ppg (GitHub-reviewed advisory GHSA-fm3m-jrgm-5ppg lists affected ranges: Go github.com/tnborg/panel >=2.3.19 =0.0.0-20241111062800-91ecd04c2700 <0.0.0-20250707071915-4985eb2e1f38)

Commands are suggestions: review each one before running it.

Loading voting…