Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.8%top 25%

CVE-2026-44590: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in sherlock-project sherlock

0
Critical
VulnerabilityCVE-2026-44590cvecve-2026-44590cwe-78
Published: Wed May 27 2026 (05/27/2026, 19:23:01 UTC)
Source: CVE Database V5
Vendor/Project: sherlock-project
Product: sherlock

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.

CVSS v3.1

Score 9.3critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/27/2026, 20:35:43 UTC

Technical Analysis

The sherlock tool, used for hunting social media accounts by username, had a command injection vulnerability in its GitHub Actions workflow validate_modified_targets.yml before version 0.16.1. The vulnerability arises from improper neutralization of special elements in OS commands (CWE-78) triggered via the pull_request_target event. This allows unauthenticated GitHub users to run arbitrary commands on the CI runner and steal the GITHUB_TOKEN without any pull request approval or merge. The issue is resolved in version 0.16.1.

Potential Impact

Successful exploitation allows an attacker to execute arbitrary OS commands on the CI runner hosting the GitHub Actions workflow. This can lead to exfiltration of the GITHUB_TOKEN, which may allow further unauthorized access to the repository or other resources accessible via the token. The vulnerability does not require any privileges or user interaction beyond opening a pull request, making it highly critical.

Mitigation Recommendations

Upgrade sherlock to version 0.16.1 or later, where this vulnerability is fixed. Since the vulnerability is in the GitHub Actions workflow, updating to the patched workflow version eliminates the risk. There is no indication of an official temporary fix or workaround; therefore, applying the official fix is necessary.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-05-06T21:49:12.425Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a17519de29bf47b50e77198

Added to database: 5/27/2026, 8:18:37 PM

Last enriched: 5/27/2026, 8:35:43 PM

Last updated: 5/29/2026, 8:42:17 PM

Views: 68

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses