# CVE-2026-16628: oclif JIT Plugin Entry child_process.exec os command injection

> Local attackers can execute arbitrary OS commands via the JIT Plugin Entry Handler in the oclif library.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-h75p-gxr9-842c

## What is CVE-2026-16628?

CVE-2026-16628 is a medium-severity command injection vulnerability in oclif, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in oclif up to 4.23.16. Affected by this vulnerability is the function child_process.exec of the component JIT Plugin Entry Handler. Performing a manipulation of the argument jitPlugins results in os command injection. The attack is only possible with local access. The exploit is now public and may be used. The patch is named 939b045725e065baebc4587b8bccfd56731eed3d. To fix this issue, it is recommended to deploy a patch.

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

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


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

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

## Is CVE-2026-16628 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16628 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16628 is a medium-severity command injection vulnerability in oclif, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16628 exists.

Affected product: oclif. 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-16628/ (Markdown: https://insights.sbomify.com/CVE-2026-16628/index.md)
```

## Sources

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

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