Quick answers
- Is CVE-2026-41473 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41473 being exploited in the wild.
- How severe is CVE-2026-41473?
- Critical severity, with a CVSS score of 9.1, published 24 April 2026.
- Which products and versions are affected?
- CyberPanel CyberPanel prior to 2.4.4.
- Is there a fix for CVE-2026-41473?
- A patch was published on 2026-04-24: Fix included in version 2.4.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41473 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41473?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass exists in CyberPanel's AI Scanner worker API due to a blanket exclusion in the security middleware (`secMiddleware.py`) for paths starting with `/api/`. Specifically, the `/api/ai-scanner/status-webhook` and `/api/ai-scanner/callback` endpoints are decorated with `@csrf_exempt` but lack any session or token-based authentication checks. A remote, unauthenticated attacker can send crafted POST requests to these endpoints to inject arbitrary JSON data into the `ScanHistory` and `ScanStatusUpdate` database tables. While the callback endpoint requires a valid `scan_id`, an attacker can obtain one by triggering a legitimate scan and then pollute the database with malicious findings, potentially leading to storage exhaustion (DoS) or XSS via the administrative UI. The vulnerability is addressed in version 2.4.4 by implementing API key validation.
Affected products
- CyberPanel CyberPanel prior to 2.4.4
Timeline
- 2025-12: disclosed: Vulnerability discovered by researchers during audit.
- 2026-01-18: advisory: Researcher blog post published.
- 2026-04-24: advisory: CVE published to NVD.
- 2026-04-24: patched: Fix included in version 2.4.4.