Vulnerability · Published May 26, 2026 · Assigned by GitHub_M

CVE-2026-44847MaxKB: Webhook Trigger Authentication Bypass

High 7.5

In plain English

A high-severity improper authentication in MaxKB from 1Panel-dev. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities).

Severity (CVSS 3.1)7.5High

Exploit odds (30 days)0.3%top 80.6% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

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.

Affected products (as reported)

Vendor	Product	Versions
1Panel-dev	MaxKB	< 2.9.0

Weakness: CWE-287, CWE-306 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

References

https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r3j3-j58q-rjpp x_refsource_CONFIRM
https://github.com/1Panel-dev/MaxKB/issues/5213 x_refsource_MISC