Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64511: CWE-918: Server-Side Request Forgery (SSRF) in 1Panel-dev MaxKB

0
High
VulnerabilityCVE-2025-64511cvecve-2025-64511cwe-918
Published: Thu Nov 13 2025 (11/13/2025, 15:51:53 UTC)
Source: CVE Database V5
Vendor/Project: 1Panel-dev
Product: MaxKB

Description

CVE-2025-64511 is a high-severity Server-Side Request Forgery (SSRF) vulnerability affecting MaxKB, an open-source AI assistant for enterprise by 1Panel-dev. Versions prior to 2. 3. 1 allow authenticated users with low privileges to execute Python code within a sandboxed tool module, which can be exploited to access internal network services such as databases. Although the code runs in a sandbox, the SSRF enables attackers to bypass network restrictions and potentially compromise confidentiality, integrity, and availability of internal resources. The vulnerability has a CVSS score of 7. 4, indicating a significant risk, especially in environments where MaxKB is deployed with sensitive internal services. No known exploits are reported in the wild yet, but patching to version 2. 3. 1 is critical.

AI-Powered Analysis

AILast updated: 11/20/2025, 16:19:55 UTC

Technical Analysis

CVE-2025-64511 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the open-source enterprise AI assistant MaxKB developed by 1Panel-dev. The vulnerability exists in versions prior to 2.3.1, where the application allows users with low privileges to execute Python code within a sandboxed environment in the tool module. Despite sandboxing, the SSRF flaw permits attackers to craft requests that reach internal network services, such as databases or other sensitive endpoints, which are normally inaccessible from outside the network. This occurs because the sandbox does not sufficiently restrict network access or validate outbound requests, enabling attackers to pivot into internal infrastructure. The vulnerability has a CVSS 3.1 base score of 7.4, reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and a scope change with partial impact on confidentiality, integrity, and availability. The flaw can lead to unauthorized data access, data manipulation, or service disruption. Although no exploits are currently known in the wild, the risk is significant given the potential for lateral movement and internal reconnaissance. Version 2.3.1 of MaxKB addresses this issue by improving sandbox restrictions and network request validation. Organizations using affected versions should apply this update promptly to prevent exploitation.

Potential Impact

For European organizations, this SSRF vulnerability poses a substantial risk to internal network security, especially for enterprises relying on MaxKB for AI-assisted operations involving sensitive data or critical infrastructure. Exploitation could lead to unauthorized access to internal databases, leakage of confidential information, data integrity compromise, and potential service outages. This is particularly concerning for sectors such as finance, healthcare, and government agencies where data confidentiality and service availability are paramount. The ability to perform SSRF with low privileges and no user interaction increases the likelihood of automated attacks or insider threats exploiting this vulnerability. Additionally, the scope change indicated in the CVSS vector suggests that the vulnerability can affect components beyond the initially compromised system, amplifying the potential damage. Given the interconnected nature of enterprise networks in Europe, a successful attack could cascade, affecting multiple systems and services.

Mitigation Recommendations

Beyond applying the official patch to upgrade MaxKB to version 2.3.1 or later, European organizations should implement several targeted mitigations: 1) Enforce strict network segmentation to isolate internal services and databases from application servers running MaxKB, limiting SSRF attack surface. 2) Deploy egress filtering and outbound request whitelisting on servers hosting MaxKB to prevent unauthorized internal network requests. 3) Monitor and log all outbound requests from MaxKB instances for unusual or unexpected destinations to detect potential exploitation attempts. 4) Conduct regular code audits and sandbox environment reviews to ensure no bypasses exist in custom or third-party modules. 5) Restrict user privileges further to minimize the number of users able to execute code within MaxKB’s tool module. 6) Implement intrusion detection systems (IDS) tuned to detect SSRF patterns and anomalous internal network traffic. 7) Educate security teams about this vulnerability and encourage proactive threat hunting for SSRF indicators in enterprise environments.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-05T21:15:39.399Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6916001feb29b6dceb02d4a4

Added to database: 11/13/2025, 3:58:23 PM

Last enriched: 11/20/2025, 4:19:55 PM

Last updated: 12/29/2025, 7:47:41 AM

Views: 132

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats