CVE-2026-77525

MaxKB: Management chat-record routes trust path application_id but load ChatRecord by global chat_id

  • Medium 4.2

Description

MaxKB is an open-source AI assistant for enterprise. In 2.10.2-lts and earlier, management chat-record routes authorize the path application_id but load records using global chat_id and chat_record_id values without confirming that the chat belongs to the authorized application. A normal user in the same workspace who knows the chat_id of a persisted non-debug record for a victim's published application can place it under a separate attacker-owned application path to read victim chat records. An attacker with an owned knowledge base and document can also use add_knowledge to copy victim answers while updating the victim record's improve_paragraph_id_list. No fixed version is available as of this review.

Key facts

Published
21 Sep 2026
Last changed
24 Sep 2026
Assigned by
GitHub_M
EPSS
0.195% likely to be exploited in the next 30 days, higher than 9.32% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 4.2CVSS 3.1, Mediumfrom the CNA (GitHub_M)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
1Panel-devMaxKB
  • <= 2.10.2-lts (affected)

Timeline

  1. 21 Sep 2026 Published

Weakness

References