CVE-2026-26396
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenBMB XAgent v1.0.0 and before is vulnerable to path traversal in the file() function in XAgent/XAgentServer/application/routers/workspace.py. The input parameter “filename” is user-controllable and is concatenated into the file path to be read without proper validation, leading to a directory traversal vulnerability that may result in sensitive information disclosure.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenBMB XAgent v1.0.0 and before contains a path traversal vulnerability in the file() function within XAgent/XAgentServer/application/routers/workspace.py. The 'filename' parameter is directly concatenated into the file path without validation, allowing attackers to use '../' sequences to read arbitrary files outside the intended directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the vulnerable source fileCheck if the file XAgent/XAgentServer/application/routers/workspace.py exists in your installation directoryAffected if the file exists and contains the file() function definition
-
Identify the installed XAgent versionRun 'pip show xagent' or check the version in your package manager, or inspect the version file in your XAgent installationAffected if the version is 1.0.0 or any version before 1.0.0
-
Verify the vulnerable code pattern existsOpen workspace.py and search for the file() function; confirm the filename parameter is directly concatenated into the path without validation (e.g., 'open(filename)' or 'Path(filename)' without sanitization)Affected if the code shows direct path concatenation without validation checks like path normalization or allowlisting
-
Check if the workspace router is enabledInspect your XAgentServer application configuration (e.g., main.py or app.py) to see if workspace.py router is included in the FastAPI/Starlette applicationAffected if the workspace router is mounted and accessible to users
-
Confirm network exposure of the endpointReview your server configuration to determine if the workspace API endpoints are exposed to untrusted users (check reverse proxy settings, firewall rules, or authentication configuration)Affected if the file() endpoint is reachable without proper authentication or from untrusted networks
You are affected if running OpenBMB XAgent version 1.0.0 or earlier with the vulnerable workspace.py file present and its file() endpoint accessible to users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the filename parameter using path normalization and allowlisting of permitted characters/patterns, combined with verification that the resolved path remains within the intended base directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26396 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data