# CVE-2026-44590: Sherlock: Command Injection via pull_request_target in validate_modified_targets.yml

> Attackers can execute arbitrary commands and steal tokens on CI runners via a malicious pull request in the Sherlock project's GitHub Actions workflow.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** UBUNTU-CVE-2026-44590

## What is CVE-2026-44590?

CVE-2026-44590 is a critical command injection vulnerability in sherlock-project sherlock, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sherlock hunts down social media accounts by username across social networks. Prior to 0.16.1, the GitHub Actions workflow validate_modified_targets.yml is vulnerable to command injection via the pull_request_target trigger. Any GitHub user can execute arbitrary commands on the CI runner and exfiltrate the GITHUB_TOKEN by opening a pull request. No approval, review, or merge is required. This vulnerability is fixed in 0.16.1.

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

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


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

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

## Is CVE-2026-44590 being exploited?

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

Public exploit code:

- CVE-2026-44590 - Sherlock <= v0.16.0 - RCE via pull_request_target Injection → Supply Chain Compromise (github_poc): https://github.com/Astaruf/CVE-2026-44590

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44590 is a critical command injection vulnerability in sherlock-project sherlock, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44590 exists.

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

## Sources

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

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