VulnerabilityPublished 13 Nov 2025

CVE-2025-64703: 1Panel-dev MaxKB · Information Exposure

Affects 1Panel-dev MaxKBSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.3.1 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.3.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade 1Panel-dev MaxKB to 2.3.1.

Affected software

Product	Affected	Fixed in
PyPImaxkb`pkg:pypi/maxkb`Other threats	Affected <2.3.1	Fixed in 2.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade all MaxKB deployments to version 2.3.1 or later immediately to apply the official fix.
Restrict access to the Python code execution tool module strictly to trusted and authenticated users with minimal privileges.
Implement robust internal access controls and monitoring to detect anomalous usage of the tool module.
Conduct regular audits of AI assistant usage and sandbox environment configurations to ensure proper isolation.
Employ network segmentation to limit exposure of MaxKB instances to only necessary internal systems.
Integrate MaxKB logs with centralized security information and event management (SIEM) systems to enable real-time alerting on suspicious activities.
Educate users and administrators about the risks of privilege misuse and enforce strong authentication mechanisms.
Consider additional sandbox hardening or containerization techniques if custom deployments are used.
Review and update incident response plans to include scenarios involving AI assistant data exposure.
Stay informed on updates from 1Panel-dev and security advisories for any further patches or mitigations.

Description

CVE-2025-64703 is a medium-severity vulnerability in the open-source AI assistant MaxKB (versions prior to 2.3.1) developed by 1Panel-dev. The flaw allows users with limited privileges to extract sensitive information via Python code execution within a sandboxed tool module. Although the process runs in a sandbox, the isolation is insufficient to prevent unauthorized data exposure. The vulnerability impacts confidentiality, integrity, and availability to a limited extent and does not require user interaction but does require some level of privilege. The issue was addressed in version 2.3.1. European organizations using vulnerable MaxKB versions may face risks of sensitive data leakage, potentially affecting enterprise AI deployments.

Impact

For European organizations, the impact of CVE-2025-64703 centers on the potential unauthorized disclosure of sensitive enterprise information handled by MaxKB AI assistant deployments. This could lead to confidentiality breaches affecting proprietary data, customer information, or internal communications. Integrity and availability impacts are assessed as low but still present, meaning that data manipulation or service disruption is possible but limited. Organizations relying on MaxKB for AI-driven knowledge management or automation may face operational risks and reputational damage if sensitive data is exposed. Given the medium severity and requirement for some privileges, the threat is more significant in environments with weak access controls or insider threats. The lack of known exploits reduces immediate risk but does not eliminate the potential for targeted attacks. European enterprises in sectors such as finance, manufacturing, and technology that integrate AI assistants like MaxKB should prioritize addressing this vulnerability to maintain compliance with data protection regulations such as GDPR and avoid costly data breaches.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/1Panel-dev/MaxKB/security/advisories/GHSA-qwvm-x4xh-g2qq (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Nov 2025, 16:20 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats