← Back
CVE-2026-28795
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in openchatbi. Attackers reach the vulnerable code path via ``save_report`` without authentication.
📍 Affected scope
openchatbi — . Attack surface: `save_report` / `file_format` / `__init__.py`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.2.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openchatbi to 0.2.2ステージング環境で 0.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
openchatbi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-28795
- advisory https://github.com/advisories/GHSA-vmwq-8g8c-jm79
- package https://github.com/zhongyu09/openchatbi
- package https://pypi.org/project/openchatbi
- web https://github.com/zhongyu09/openchatbi/security/advisories/GHSA-vmwq-8g8c-jm79
- web https://github.com/zhongyu09/openchatbi/issues/10
- web https://github.com/zhongyu09/openchatbi/pull/12
- web https://github.com/zhongyu09/openchatbi/commit/372a7e861da5159c3106d64d6f6edf8284db8c75