CVE Vulnerability Catalog

MCPHub in versions below 0.11.0 is vulnerable to authentication bypass. Some endpoints are not protected by authentication middleware, allowing an unauthenticated attacker to perform actions in the name of other users and using their privileges.

The ExtractEmbeddedFiles example in Apache PDFBox (versions 2.0.24–2.0.36 and 3.0.0–3.0.7) contains a path traversal vulnerability (CWE-22). The fix in 2.0.36 and 3.0.7 is flawed because it does not consider the file path separator, allowing writes to paths starting with the user's directory, e.g. /home/ABCDEF.

In Apache APISIX, the tencent-cloud-cls log export uses plaintext HTTP, which may lead to cleartext transmission of sensitive information. The vulnerability affects versions from 2.99.0 through 3.15.0.

MaxKB versions 2.7.1 and below contain a Stored XSS vulnerability where the frontend's MdRenderer.vue component parses custom <iframe_render> tags from LLM responses or Application Prologue configurations, bypassing Markdown sanitization and XSS filtering. The unsanitized HTML is passed to IframeRender.vue and rendered into an iframe via srcdoc with sandbox="allow-scripts allow-same-origin", allowing injected scripts to escape the iframe and execute JavaScript in the parent window.

MaxKB versions 2.7.1 and below contain a Stored Cross-Site Scripting (XSS) vulnerability that allows authenticated users to inject arbitrary HTML and JavaScript into the Application prologue (Opening Remarks) field by wrapping malicious payloads in <html_rander> tags. The backend fails to sanitize or encode HTML entities in the prologue field, and the frontend renders this content using an innerHTML-equivalent mechanism, enabling persistent DOM-based Stored XSS against any visitor who opens the affected chatbot interface. The issue has been fixed in version 2.8.0.

MaxKB versions 2.7.1 and below are vulnerable to Improper Neutralization of Formula Elements in a CSV File. When an administrator exports chat history to an Excel file (.xlsx), strings starting with formula characters are written without proper sanitization, which can lead to Arbitrary Code Execution (RCE) on the administrator's workstation via Dynamic Data Exchange (DDE) when opened in spreadsheet applications like Microsoft Excel.

MaxKB versions 2.7.1 and below contain an Eval Injection vulnerability in the Markdown rendering engine that lets any user of the AI chat interface execute arbitrary JavaScript in other users' browsers, including administrators, resulting in Stored XSS. The issue is fixed in version 2.8.0.

MaxKB versions 2.7.1 and below contain a stored XSS vulnerability through the application name or icon fields when creating an application. When a victim visits the public chat interface (/ui/chat/{access_token}), ChatHeadersMiddleware retrieves application data and directly inserts the unescaped application name and icon into the HTML response via string replacement. This allows an attacker to execute arbitrary JavaScript in the victim's browser context.

MaxKB is an open-source AI assistant for enterprise. Versions 2.7.1 and below contain a sandbox escape vulnerability in the ToolExecutor component. By leveraging Python's ctypes library to execute raw system calls, an authenticated attacker with workspace privileges can bypass the LD_PRELOAD-based sandbox.so module to achieve arbitrary code execution, enabling full network exfiltration and container compromise. This issue has been fixed in version 2.8.0.

MaxKB versions 2.7.1 and below have an incomplete LD_PRELOAD-based sandbox that an authenticated user with tool execution privileges can escape. Using the env command, an attacker can clear environment variables and drop the sandbox.so hook, leading to unrestricted Remote Code Execution (RCE) and network access. This issue has been fixed in version 2.8.0.

MaxKB versions 2.7.1 and below allow bypassing sandbox network protection using socket.sendto() with the MSG_FASTOPEN flag. An authenticated user with tool-editing permissions can reach internal services blocked by the banned hosts configuration.

During authorization checks in SAP Human Capital Management for SAP S/4HANA, the system returns specific messages. As a result, an authenticated low-privileged user could guess and enumerate content beyond their authorized scope, leading to disclosure of sensitive information with high impact on confidentiality while integrity and availability are unaffected.

Information Disclosure Vulnerability in SAP HANA Cockpit and HANA Database Explorer. Technical details were not provided in the description.

Due to a missing authorization check in SAP Business Analytics and SAP Content Management, an authenticated user could make unauthorized calls to certain remote function modules, potentially accessing sensitive information beyond their intended permissions. This vulnerability affects confidentiality, with no impact on integrity and availability.

W wyniku podatności typu Open Redirect w SAP NetWeaver Application Server ABAP, nieautoryzowany atakujący może stworzyć złośliwy adres URL, który po otwarciu przez ofiarę przekieruje ją na stronę kontrolowaną przez atakującego. Podatność ta ma niski wpływ na poufność i integralność aplikacji, nie wpływając na dostępność.

MaxKB versions 2.7.1 and below contain an incomplete fix for CVE-2025-53928, leaving a Remote Code Execution vulnerability in the MCP node of the workflow engine. The fix only restricts the referencing code path, while the else branch loading mcp_servers directly from user-supplied JSON remains unpatched, allowing bypass and remote code execution.

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. In versions 1.2.2 and below, an unauthenticated p2p peer can cause the RequestMacroChain message handler task to panic by sending a RequestMacroChain message where the first locator hash on the victim's main chain is a micro block hash instead of a macro block hash; this is fixed in version 1.3.0.

jq is a command-line JSON processor. Commits before 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b contain a vulnerability where CLI input parsing allows validation bypass via embedded NUL bytes. When reading JSON from files or stdin, jq uses strlen() to determine buffer length instead of the actual byte count from fgets(), causing it to truncate input at the first NUL byte and parse only the preceding prefix. This enables an attacker to craft input with a benign JSON prefix before a NUL byte followed by malicious trailing data, where jq validates only the prefix as valid JSON while silently discarding the suffix. Workflows relying on jq to validate untrusted JSON before forwarding it to downstream consumers are susceptible to parser differential attacks, as those consumers may process the full input including the malicious trailing bytes. This issue has been patched by commit 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b.

SAP BusinessObjects Business Intelligence allows an authenticated attacker to inject malicious JavaScript payloads through crafted URLs. When a victim accesses the URL, the script executes in the user's browser, potentially exposing restricted information.

Due to missing authorization checks in the SAP S/4HANA frontend OData Service (Manage Reference Structures), an attacker could update and delete child entities via exposed OData services without proper authorization. This vulnerability has a high impact on integrity, while confidentiality and availability are not impacted.