Skip to main content
VulnerabilityPublished

CVE-2026-44590: sherlock · OS Command Injection

Affects sherlockSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 0.16.1 as a priority.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.16.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade sherlock and sherlock-project/sherlock to 0.16.1.

Affected software

ProductAffectedFixed in
sherlock-projectsherlockAffected
  • <0.16.1
Fixed in
  • 0.16.1
GitHubsherlock-project/sherlockpkg:github/sherlock-project/sherlockOther threatsAffected
  • <0.16.1
Fixed in
  • 0.16.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade sherlock to version 0.16.1 or later, where this vulnerability is fixed. Until upgrading, avoid running untrusted pull requests on workflows triggered by pull_request_target events. Patch status is not explicitly stated but the vendor fixed the issue in version 0.16.1, so applying this update is the recommended remediation.

Description

CVE-2026-44590 is a critical OS command injection vulnerability in the sherlock-project's sherlock tool prior to version 0.16.1. The flaw exists in the GitHub Actions workflow validate_modified_targets.yml, which is triggered by pull_request_target events. An attacker can exploit this by opening a pull request to execute arbitrary commands on the CI runner without needing approval, review, or merge. This can lead to exfiltration of the GITHUB_TOKEN, potentially compromising repository credentials. The vulnerability is fixed in version 0.16.1.

References

Community reviews

Loading reviews…