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 · Vendor: vuldb
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS 4.0 vector indicates remote network-based attack (AV:N) with low complexity (AC:L) requiring high privileges (PR:H) and no user interaction (UI:N), resulting in low confidentiality impact (VC:L). The exploitation phase is marked as published (E:P), confirming public exploit code availability. While the CVSS base score of 5.1 appears moderate, the real-world risk is elevated by two factors: (1) the public availability of exploit code lowers the barrier to exploitation, and (2) the requirement for high privileges (PR:H) significantly constrains the threat actor pool to administrators or highly privileged users already within the trust boundary. The information disclosure impact is limited to confidentiality with no integrity or availability impact. This vulnerability should be prioritized for patching in environments where XAgent is deployed with sensitive API keys, but it does not represent a critical threat to unauthenticated or low-privilege users.

Exploit ScenarioDerived

A system administrator with high-privilege access to an OpenBMB XAgent deployment intentionally or unintentionally reviews application log files (via direct file access, log aggregation platform, or monitoring dashboard) and extracts plaintext API credentials that were logged as a side effect of the handle_tool_call function processing API key arguments. The attacker then uses the extracted credentials to authenticate to third-party services or APIs that the XAgent instance communicates with, enabling lateral movement or unauthorized data access. Publicly available exploit code exists that documents or automates this credential extraction from logs.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 27, 2026

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.

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.

Affected VersionsENISA

XAgent 1.0.0

Affected Packages

euvd xagent no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

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.

Know when Xagent gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) 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

Primary rating from Vendor (vuldb) · only source for this CVE.

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Apr 29, 2026 - 01:11 NVD
MEDIUM LOW
CVSS changed
Apr 29, 2026 - 01:11 NVD
5.1 (MEDIUM) 2.0 (LOW)
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.

Executive ViewAI

Why It Matters

Organizations using A flaw should be aware of moderate risk from CVE-2026-4957, a information exposure vulnerability rated CVSS 5.1. Sensitive information could be exposed to unauthorized parties. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict endpoint access, redact sensitive data in logs.

Threat Intelligence Overview

EPSS Score
0.0%
Top 93% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Low
Technical Impact
Partial

Priority Score

10
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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