VulnerabilityPublished 11 Mar 2026

CVE-2026-3954: OpenBMB XAgent · Path Traversal

Affects OpenBMB XAgentSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
OpenBMBXAgent	Affected =1.0.0	Fixed in–
GitHubopenbmb/XAgent`pkg:github/openbmb/XAgent`Other threats	Affected =1.0.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:openbmb:xagent:*:*:*:*:*:*:*:*

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

AI-suggested

To mitigate CVE-2026-3954, organizations should immediately restrict network access to the OpenBMB XAgent service, limiting it to trusted internal users and systems. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal patterns in HTTP requests targeting the workspace function. Conduct thorough input validation and sanitization on the file_name parameter to reject traversal sequences and enforce strict allowlists for acceptable file paths. Monitor logs for suspicious access attempts involving unusual file paths or traversal characters. If possible, deploy application-layer sandboxing or containerization to limit the impact of unauthorized file access. Engage with the OpenBMB project or community to obtain updates or patches and apply them promptly once available. As a temporary workaround, consider disabling or restricting the vulnerable workspace functionality if it is not essential. Regularly audit and review file permissions on the server to minimize exposure of sensitive files. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Description

CVE-2026-3954 is a path traversal vulnerability in OpenBMB XAgent version 1.0.0, specifically in the workspace function of the file XAgentServer/application/routers/workspace.py. This flaw allows remote attackers to manipulate the file_name argument to access files outside the intended directory. The vulnerability requires no authentication or user interaction and has a CVSS 4.0 base score of 6.9, indicating medium severity. Although the exploit code is publicly available, no known active exploitation has been reported. The OpenBMB project has been informed but has not yet issued a patch.

Impact

The primary impact of CVE-2026-3954 is unauthorized access to files on the server hosting OpenBMB XAgent 1.0.0. Attackers can read sensitive configuration files, credentials, or other data that should be protected, potentially leading to further compromise of the system or network. The ability to access arbitrary files can also facilitate reconnaissance and lateral movement within an organization’s infrastructure. Although the vulnerability does not directly allow code execution, the exposure of sensitive information can enable subsequent attacks. The lack of authentication and user interaction requirements increases the risk of automated exploitation attempts. Organizations relying on OpenBMB XAgent for critical operations may face data confidentiality breaches and operational disruptions. The absence of an official patch prolongs exposure and complicates risk management. Overall, the vulnerability poses a moderate risk but could escalate if combined with other weaknesses or targeted in high-value environments.

References

Community reviews

Loading reviews…