← Back
CVE-2026-40112
Cross-Site Scripting (XSS) in praisonai (CVE-2026-40112)
Summary
cross-site scripting in praisonai (CVE-2026-40112). Risk of unauthorized operations or information disclosure. Exploitable via ``_sanitize_html``. Mitigation: upgrade to `4.5.128` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40112** has been found in praisonai.
Attackers can target a specific entry point like ``_sanitize_html`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade praisonai to **4.5.128** or later.
If unsure, ask your IT team or search "praisonai CVE-2026-40112" on the vendor's site.
CVE-2026-40112 (praisonai) — CWE-79 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `_sanitize_html` / `nh3` / `pyproject.toml` / `markdown`
Patched: `4.5.128` — 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
**Cross-site scripting (XSS)** (CWE-79) exists in praisonai. Attackers reach the vulnerable code path via ``_sanitize_html`` without authentication.
📍 Affected scope
praisonai — . Attack surface: `_sanitize_html` / `nh3` / `pyproject.toml` / `markdown`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.5.128**.
🛡️ 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 'praisonai' .` 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 'praisonai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `praisonai` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade praisonai to 4.5.128ステージング環境で 4.5.128 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
praisonai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.128"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40112
- advisory https://github.com/advisories/GHSA-cfg2-mxfj-j6pw
- package https://github.com/MervinPraison/PraisonAI
- package https://pypi.org/project/praisonai
- web https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-cfg2-mxfj-j6pw
- web https://github.com/MervinPraison/PraisonAI/releases/tag/v4.5.128