Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-85013 high CVSS 7.3

OS Command Injection in environment-modules (CVE-2026-85013)

Summary

OS command injection in environment-modules (CVE-2026-85013). Successful exploitation can lead to full system takeover. Exploitable via MODULEPATH.

Original description

The description as published by the source.

A flaw was found in environment-modules. A local attacker can exploit this vulnerability by placing a maliciously named modulefile in a location visible to the victim's MODULEPATH. When the victim uses Bash completion for module or ml commands, the malicious module name, containing shell metacharacters, is evaluated as a command. This can lead to arbitrary command execution in the completing user's shell, impacting their confidentiality, integrity, and availability.

Source: NIST National Vulnerability Database NVD

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-85013 has been found in environment-modules.
Attackers can target a specific entry point like MODULEPATH over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "environment-modules CVE-2026-85013" on the vendor's site.

CVE-2026-85013 (environment-modules) — CWE-78 / CVSS v3 7.3
Attack vector: local
Attack surface: MODULEPATH / module
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

OS command injection (CWE-78) exists in environment-modules. Attackers reach the vulnerable code path via MODULEPATH.

📍 Affected scope

Check the vendor advisory for the affected versions of environment-modules. Attack surface: MODULEPATH / module.

🔥 Severity

Severity: High (CVSS 7.3/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 'environment-modules' . 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

  1. 1
    Identify exposure identify 
    grep -r 'environment-modules' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で environment-modules を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details