{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44590 exists.","fix":"No fix has been published for CVE-2026-44590 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-44590 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44590 exists.\n\nAffected product: sherlock-project sherlock. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44590/ (Markdown: https://insights.sbomify.com/CVE-2026-44590/index.md)","id":"CVE-2026-44590","markdown":"https://insights.sbomify.com/CVE-2026-44590/index.md","name":"CVE-2026-44590","record":{"aliases":["UBUNTU-CVE-2026-44590"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sherlock GitHub Actions","requires_auth":"none","summary":"Attackers can execute arbitrary commands and steal tokens on CI runners via a malicious pull request in the Sherlock project's GitHub Actions workflow.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-07T19:16:06Z","kind":"github_poc","ref":"https://github.com/Astaruf/CVE-2026-44590","stars":0,"title":"CVE-2026-44590 - Sherlock \u003c= v0.16.0 - RCE via pull_request_target Injection → Supply Chain Compromise"}],"tier":"weaponised"},"has_fix":false,"headline":"Sherlock: Command Injection via pull_request_target in validate_modified_targets.yml","id":"CVE-2026-44590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Gradient: Unauthenticated worker on /proto → arbitrary NAR write / cache poisoning","id":"CVE-2026-44592"},"packages":[],"prev":{"headline":"nuxt-og-image SSRF — bypass of GHSA-pqhr-mp3f-hrpp / v6.2.5 fix (IPv6 + redirect)","id":"CVE-2026-44589"},"products":["sherlock"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["sherlock-project"]},"summary":"Attackers can execute arbitrary commands and steal tokens on CI runners via a malicious pull request in the Sherlock project's GitHub Actions workflow.","url":"https://insights.sbomify.com/CVE-2026-44590/"}