1Panel-dev MaxKB up to 2.8.x WebHook Trigger /api/trigger/v1/webhook/ WebhookAuth improper authentication

Summaryinfo

A vulnerability, which was classified as critical, has been found in 1Panel-dev MaxKB up to 2.8.x. Impacted is the function WebhookAuth of the file /api/trigger/v1/webhook/ of the component WebHook Trigger Handler. This manipulation causes improper authentication. This vulnerability is handled as CVE-2026-44847. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in 1Panel-dev MaxKB up to 2.8.x. It has been declared as critical. Affected by this vulnerability is the function WebhookAuth of the file /api/trigger/v1/webhook/ of the component WebHook Trigger Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

MaxKB is an open-source AI assistant for enterprise. Prior to 2.9.0, MaxKB's webhook trigger endpoint (/api/trigger/v1/webhook/{trigger_id}) is accessible without authentication. The WebhookAuth class unconditionally returns (None, {}), which Django REST Framework interprets as successful authentication. Combined with optional per-trigger token verification and no backend enforcement of token requirements, any unauthenticated attacker who knows a valid trigger ID can invoke webhook triggers to execute their bound tasks. This vulnerability is fixed in 2.9.0.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-44847 since 05/07/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.

Upgrading to version 2.9.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-31987). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• 1Panel-dev

Name

• MaxKB

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8

Website

• Product: https://github.com/1Panel-dev/MaxKB/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion