CVE-2026-44847: CWE-287: Improper Authentication in 1Panel-dev MaxKB
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.
AI Analysis
Technical Summary
MaxKB versions before 2.9.0 contain an improper authentication vulnerability (CWE-287) in the webhook trigger endpoint. The WebhookAuth class returns (None, {}) unconditionally, which Django REST Framework treats as successful authentication. Since token verification is optional and not enforced by the backend, attackers can invoke webhook triggers by supplying a valid trigger ID without authenticating. This can lead to unauthorized execution of bound tasks. The issue is resolved in MaxKB 2.9.0.
Potential Impact
An unauthenticated attacker who knows a valid trigger ID can invoke webhook triggers and execute their bound tasks without authorization. This could lead to unauthorized actions within the MaxKB environment. There is no indication of confidentiality or availability impact, but integrity is impacted due to unauthorized task execution. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade MaxKB to version 2.9.0 or later, where this authentication bypass vulnerability is fixed. Since no official patch links or vendor advisories are provided, verify the upgrade from the official 1Panel-dev MaxKB release notes or repository. Until upgraded, restrict access to the webhook endpoint to trusted networks or implement external access controls to prevent unauthorized trigger invocation.
CVE-2026-44847: CWE-287: Improper Authentication in 1Panel-dev MaxKB
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.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MaxKB versions before 2.9.0 contain an improper authentication vulnerability (CWE-287) in the webhook trigger endpoint. The WebhookAuth class returns (None, {}) unconditionally, which Django REST Framework treats as successful authentication. Since token verification is optional and not enforced by the backend, attackers can invoke webhook triggers by supplying a valid trigger ID without authenticating. This can lead to unauthorized execution of bound tasks. The issue is resolved in MaxKB 2.9.0.
Potential Impact
An unauthenticated attacker who knows a valid trigger ID can invoke webhook triggers and execute their bound tasks without authorization. This could lead to unauthorized actions within the MaxKB environment. There is no indication of confidentiality or availability impact, but integrity is impacted due to unauthorized task execution. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade MaxKB to version 2.9.0 or later, where this authentication bypass vulnerability is fixed. Since no official patch links or vendor advisories are provided, verify the upgrade from the official 1Panel-dev MaxKB release notes or repository. Until upgraded, restrict access to the webhook endpoint to trusted networks or implement external access controls to prevent unauthorized trigger invocation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-07T21:21:48.353Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a16041de29bf47b505ea06f
Added to database: 05/26/2026, 20:35:41 UTC
Last enriched: 06/03/2026, 20:28:16 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 81
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.