Path Traversal in openchatbi (CVE-2026-28795)
Summary
Path traversal in openchatbi (CVE-2026-28795). Risk of unauthorized operations or information disclosure. Exploitable via save_report. Mitigation: upgrade to 0.2.2 or later.
Original description
The description as published by the source.
Impact
The save_report tool in openchatbi/tool/save_report.py suffers from a critical path traversal vulnerability due to insufficient input sanitization of the file_format parameter.
The function only removes leading dots of file_format using file_format.lstrip(".") but allows path traversal sequences like /../../ to pass through unchanged. When the filename is constructed via string concatenation in
f"{timestamp}_{clean_title}.{file_format}"
malicious path sequences are preserved, enabling attackers to write files outside the designated report directory.
An attacker can manipulate the LLM to call the tool with a specific file_format to overwrite critical system files like __init__.py, potentially leading to remote code execution.
Patches
- Affected versions:
<=0.2.1 - Patched versions:
0.2.2 (includes fix from PR #12: https://github.com/zhongyu09/openchatbi/pull/12)
Workarounds
No
References
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-28795 has been found in openchatbi.
Attackers can target a specific entry point like save_report over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openchatbi to 0.2.2 or later.
If unsure, ask your IT team or search "openchatbi CVE-2026-28795" on the vendor's site.
CVE-2026-28795 (openchatbi) — CWE-22
Attack surface: save_report / file_format / __init__.py
Patched: 0.2.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in openchatbi. Attackers reach the vulnerable code path via save_report.
Check the vendor advisory for the affected versions of openchatbi. Attack surface: save_report / file_format / __init__.py.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.2.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openchatbi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openchatbi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openchatbiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openchatbi to 0.2.2ステージング環境で 0.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com