CVE-2026-44847 MaxKB: Webhook Trigger Authentication Bypass
Unauthenticated attackers can invoke webhook triggers to execute bound tasks due to missing authentication checks in MaxKB.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-44847?
CVE-2026-44847 is a high-severity authentication bypass vulnerability in 1Panel-dev MaxKB, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
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.
Which versions are affected by CVE-2026-44847?
How do I fix CVE-2026-44847?
No fix has been published for CVE-2026-44847 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-44847 being exploited?
There is no known exploitation of CVE-2026-44847 in the wild and no public exploit code.
Sources
Also known as GHSA-r3j3-j58q-rjpp.