Quick answers
- Is CVE-2026-44847 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44847 being exploited in the wild.
- How severe is CVE-2026-44847?
- High severity, with a CVSS score of 7.5, published 26 May 2026.
- Which products and versions are affected?
- 1Panel-dev MaxKB < 2.9.0.
- Is there a fix for CVE-2026-44847?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44847 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44847?
- Check whether you run 1Panel-dev MaxKB at an affected version. 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
The vulnerability exists in the MaxKB webhook trigger endpoint (/api/trigger/v1/webhook/{trigger_id}). The 'WebhookAuth' class incorrectly returns (None, {}) during authentication, which the Django REST Framework interprets as a successful authentication signal. Furthermore, while the application supports token-based verification, it is only enforced if a token is explicitly defined in the trigger settings; the backend does not mandate token creation for EVENT-type triggers. An attacker with knowledge of a valid trigger ID can invoke the webhook to execute associated tasks, including custom Python code via 'ToolExecutor.exec_code()', potentially leading to remote code execution if the sandbox is disabled. This issue is resolved in version 2.9.0 by enforcing token requirements and correcting the authentication return values.
Affected products
- 1Panel-dev MaxKB < 2.9.0
Timeline
- 2026-05-13: advisory: GitHub Security Advisory published
- 2026-05-26: disclosed: CVE published to NVD