OS Command Injection in openlearnx (CVE-2026-41900)
Summary
OS command injection in openlearnx (CVE-2026-41900). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.0.3 or later.
Original description
The description as published by the source.
OpenLearnX is an open-source, decentralized learning and assessment platform. Prior to version 2.0.3, a remote code execution (RCE) vulnerability was identified in the OpenLearnX code execution environment, allowing sandbox escape and arbitrary command execution. This issue has been patched in version 2.0.3.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-41900 has been found in openlearnx.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade openlearnx to 2.0.3 or later.
If unsure, ask your IT team or search "openlearnx CVE-2026-41900" on the vendor's site.
CVE-2026-41900 (openlearnx) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.3 — 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.
OS command injection (CWE-78) exists in openlearnx.
Check the vendor advisory for the affected versions of openlearnx.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.0.3.
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 'openlearnx' . 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 'openlearnx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openlearnxを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openlearnx to 2.0.3ステージング環境で 2.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com