What is the CVSS score of CVE-2026-41900?

CVE-2026-41900 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.4%.

Which versions of OpenLearnX are affected by CVE-2026-41900?

OpenLearnX (npm package, versions before 2.0.3) contains a vulnerability allowing any authenticated user with low privilege to execute arbitrary OS commands on the host system.. A patch is available.

How to fix or mitigate CVE-2026-41900?

Within 24 hours, inventory all systems and dependencies using openlearnx and document current installed versions. Within 7 days, upgrade all affected instances to OpenLearnX version 2.0.3 or later and validate patches in staging environments. Within 30 days, confirm all production deployments are patched, review endpoint access logs for exploitation attempts during the vulnerability window, and document remediation completion.

OpenLearnX CVE-2026-41900

HIGH

OS Command Injection (CWE-78)

2026-04-23 https://github.com/th30d4y/OpenLearnX

GHSA-8h25-q488-4hxw

RCE Command Injection

8.8

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

9.9 CRITICAL

Network-reachable code-run feature usable by any low-priv account (PR:L, AC:L, UI:N); sandbox escape crosses into the host trust boundary, so S:C, with full host C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:33 vuln.today

Analysis Generated

Jul 24, 2026 - 03:33 vuln.today

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:46 nvd

HIGH 8.8

DescriptionGitHub Advisory

Overview

A critical Remote Code Execution (RCE) vulnerability was identified in the OpenLearnX code execution environment, allowing sandbox escape and arbitrary command execution. The issue has been fixed.

AnalysisAI

Remote code execution in OpenLearnX (npm package openlearnx) before 2.0.3 lets an authenticated low-privilege user escape the Python code-execution sandbox and run arbitrary OS commands on the host. Because submitting code to the compiler/execution environment is the platform's intended feature, any user with access to that endpoint can weaponize it. Classified CWE-78 (OS command injection); no public exploit identified at time of analysis, EPSS 0.41% (61th percentile), and the flaw is fixed in 2.0.3.

Technical ContextAI

OpenLearnX is an open-source interactive coding/learning platform (Flask/Python backend, distributed via npm) that runs student-submitted code in a supposed-secure execution environment. The vulnerability is a sandbox escape in that code-execution component, mapped to CWE-78 (Improper Neutralization of Special Elements used in an OS Command), meaning user-controlled input reaches an OS-level command context. The patch commit (14765d7) reworks backend/routes/coding.py to route execution through a new 'real_compiler_service' that executes in a hardened Docker sandbox and adds security-violation logging and a dedicated execution-log stream in admin.py, indicating the pre-2.0.3 execution path did not adequately confine user code before it could invoke host commands. Affected CPE is pkg:npm/openlearnx.

RemediationAI

Vendor-released patch: 2.0.3 - upgrade the openlearnx package to 2.0.3 or later (release tag v2.0.3-security-fix), which routes code execution through the hardened Docker-based real_compiler_service and adds security-violation logging; see the advisory at https://github.com/th30d4y/OpenLearnX/security/advisories/GHSA-8h25-q488-4hxw and the fix commit https://github.com/th30d4y/OpenLearnX/commit/14765d7d1856d564747c55c5412e2f38feab079e. If immediate upgrade is not possible, restrict access to the code-execution/compiler endpoint (e.g. disable or gate the interactive code-run feature and require trusted, vetted accounts rather than open self-registration), and run the backend container with least privilege (non-root, dropped capabilities, read-only filesystem, no host network) so that any escape yields minimal host impact - with the trade-off that disabling code execution removes the platform's primary learning functionality and container hardening may break legitimate compiler features. Monitor the new execution log stream (/logs/executions) and security_logs for blocked/violation events once patched.