# CVE-2026-36044: Command injection in n/a

> Attackers can execute arbitrary OS commands via unsanitized inputs in the smart_enumerate tool of the @pensar/apex library.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-r7p8-h82j-w6x6

## What is CVE-2026-36044?

CVE-2026-36044 is a high-severity command injection vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

@pensar/apex <= 0.0.58 is vulnerable to OS command injection via the smart_enumerate tool. The createSmartEnumerateTool() function in src/core/agent/tools.ts constructs a shell command by concatenating unsanitized values from the extensions array and url parameter into a string passed to Node.js child_process.exec(). Because exec() spawns a shell, shell metacharacters in those values are interpreted by the host shell, resulting in arbitrary OS command execution with the privileges of the running process. NOTE: this is disputed by the Supplier because the report is about intended behavior, as explained in the Security Policy of the pensarai/apex GitHub repo.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-36044?


## How do I fix CVE-2026-36044?

No fix has been published for CVE-2026-36044 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-36044 being exploited?

There is no known exploitation of CVE-2026-36044 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-36044 and fix it if it is affected.

What it is: CVE-2026-36044 is a high-severity command injection vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-36044 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-36044/ (Markdown: https://insights.sbomify.com/CVE-2026-36044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-36044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-36044
- OSV: https://osv.dev/vulnerability/CVE-2026-36044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-36044/
Summaries are generated and may contain mistakes; the official description above is the record.