← Back
CVE-2026-26717
Vulnerability in richie (CVE-2026-26717)
Summary
vulnerability in richie (CVE-2026-26717). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-26717** has been found in richie.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade richie to **3.3.0** or later.
If unsure, ask your IT team or search "richie CVE-2026-26717" on the vendor's site.
CVE-2026-26717 (richie) — CWE-208 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.3.0` — 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
**A vulnerability** (CWE-208) exists in richie.
📍 Affected scope
richie — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.3.0**.
🛡️ 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 'richie' .` 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 'richie' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `richie` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade richie to 3.3.0ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
richie
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-26717
- advisory https://github.com/advisories/GHSA-xjhr-fm27-4hmx
- package https://github.com/openfun/richie
- package https://pypi.org/project/richie
- web https://github.com/openfun/richie/commit/a1b5bbda3403d7debb466c303a32852925fcba5f
- web https://github.com/Rickidevs/CVE-2026-26717
- web https://medium.com/@ordogh/cve-2026-26717-hmac-timing-attack-in-openfun-richie-lms-f04377efe83d?postPublishedType=repub