CVE-2025-53534 — panel
Fix: tnborg/panel@ed5c74cCVE-2025-53534 is a CWE-305 vulnerability in github.com/tnborg/panel. A fix is available for github.com/tnborg/panel — see the affected versions and patch details below.
RatPanel can perform remote command execution without authorization
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-53534.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/tnborg/panel🐹github.com/tnborg/panelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
RatPanel is a server operation and maintenance management panel. In versions 2.3.19 through 2.5.5, 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. RatPanel uses the CleanPath middleware provided by github.com/go-chi/chi package to clean URLs, but but the middleware does not process r.URL.Path, which can cause the paths to be misinterpreted. This is fixed in version 2.5.6.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/tnborg/panel | ≥ 2.3.19&&< 2.5.6 | 2.5.6go get github.com/tnborg/panel@v2.5.6 |
| 🐹Go | github.com/tnborg/panel | ≥ 0.0.0-20241111062800-91ecd04c2700&&< 0.0.0-20250707071915-4985eb2e1f38 | 0.0.0-20250707071915-4985eb2e1f38go get github.com/tnborg/panel@v0.0.0-20250707071915-4985eb2e1f38 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tnborg/panel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/tnborg/panel to 2.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-53534 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-53534 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-53534. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-53534 in your dependencies?
O3 Security finds CVE-2025-53534 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.