Skip to main content

Xagent CVE-2026-4957

| EUVDEUVD-2026-16658 LOW
Information Exposure (CWE-200)
2026-03-27 cna@vuldb.com GHSA-hp6g-348q-ppq3
2.0
CVSS 4.0 · NVD

Severity by source

NVD PRIMARY
2.0 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
X

Lifecycle Timeline

5
Severity Changed
Apr 29, 2026 - 01:11 NVD
MEDIUM LOW
CVSS changed
Apr 29, 2026 - 01:11 NVD
5.1 (MEDIUM) 2.0 (LOW)
EUVD ID Assigned
Mar 27, 2026 - 15:22 euvd
EUVD-2026-16658
Analysis Generated
Mar 27, 2026 - 15:22 vuln.today
CVE Published
Mar 27, 2026 - 15:17 nvd
MEDIUM 5.1

DescriptionCVE.org

A flaw has been found in OpenBMB XAgent 1.0.0. The impacted element is the function FunctionHandler.handle_tool_call of the file XAgent/function_handler.py of the component API Key Handler. This manipulation of the argument api_key causes sensitive information in log files. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

AnalysisAI

OpenBMB XAgent 1.0.0 exposes sensitive API credentials in log files through improper handling of the api_key argument in the FunctionHandler.handle_tool_call function, allowing remote authenticated attackers with high privileges to disclose confidential information. The vulnerability is classified as information disclosure (CWE-200) with a CVSS score of 5.1 and has publicly available exploit code; however, the vendor has not responded to early disclosure notification.

Technical ContextAI

The vulnerability exists in the API Key Handler component of XAgent, specifically in the file XAgent/function_handler.py where the FunctionHandler.handle_tool_call function processes API key arguments without proper sanitization before logging. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) indicates that confidential data-in this case cryptographic credentials-are being written to log files where they may be accessed by unauthorized parties. The root cause appears to be inadequate input sanitization and logging controls in the function's handling of the api_key parameter, which is then persisted in plaintext or insufficiently masked form in application logs accessible to high-privilege users.

RemediationAI

Upgrade OpenBMB XAgent to a patched version if available from the vendor; however, no specific fix version is confirmed in the provided intelligence data, and the vendor has not responded to early disclosure attempts. Immediate interim mitigations should include: (1) restricting access to application log files to the minimum set of authorized users, (2) implementing log redaction or masking rules to automatically sanitize API keys from log output before persistence, (3) using environment variables or secure configuration management systems (e.g., HashiCorp Vault, AWS Secrets Manager) to inject API credentials at runtime rather than passing them as function arguments, and (4) monitoring log files for accidental credential exposure. Monitor OpenBMB's official repository and the VulDB references at https://vuldb.com/?id.353834 for patch availability announcements.

Share

CVE-2026-4957 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy