{"answers":{"affected":"1 open source package ship an affected version, including gouef/githubtoplanguages.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58502 exists.","fix":"Upgrade gouef/githubtoplanguages to 1.1.4 or later.","what":"CVE-2026-58502 is a high-severity command injection vulnerability in gouef githubtoplanguages, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58502 and fix it if it is affected.\n\nWhat it is: CVE-2026-58502 is a high-severity command injection vulnerability in gouef githubtoplanguages, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58502 exists.\n\nAffected packages and fixed versions:\n- gouef/githubtoplanguages (GitHub Actions): affected all versions; fixed in 1.1.4\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-58502/ (Markdown: https://insights.sbomify.com/CVE-2026-58502/index.md)","id":"CVE-2026-58502","markdown":"https://insights.sbomify.com/CVE-2026-58502/index.md","name":"CVE-2026-58502","record":{"aliases":["GHSA-c3xh-98xp-6qhf"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflow","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands on GitHub Actions runners via malicious issue titles, potentially exposing secrets and spoofing notifications.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"githubtoplanguages generates a user's top GitHub languages as an SVG. The .github/workflows/discord-issue.yml workflow runs when an issue is opened or closed and interpolates github.event.issue.title directly into the Bash assignment for ISSUE_TITLE before shell parsing. An issue title containing shell command-substitution syntax can therefore execute commands on the GitHub Actions runner before the title is included in the Discord notification sent through DISCORD_WEBHOOK. Successful exploitation can manipulate or spoof trusted bot notifications and may expose the Discord webhook secret or other workflow environment data, depending on repository permissions. This issue is fixed by commit 6bf9c3a9cb66c937b9047ca266b3d02f2bb11027.","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"githubtoplanguages: Command Injection via Issue Title in Discord Notification Workflow","id":"CVE-2026-58502","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Frappe: Unauthenticated User Enumeration via reset_password","id":"CVE-2026-58503"},"packages":[{"ecosystem":"GitHub Actions","fixed":["1.1.4"],"introduced":["0"],"last_affected":[],"package":"gouef/githubtoplanguages","purl":null,"source":"GHSA-c3xh-98xp-6qhf"}],"prev":{"headline":"Zeep SSRF because Settings.forbid_external is not enforced","id":"CVE-2026-58501"},"products":["githubtoplanguages"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["gouef"]},"summary":"Attackers can execute arbitrary commands on GitHub Actions runners via malicious issue titles, potentially exposing secrets and spoofing notifications.","url":"https://insights.sbomify.com/CVE-2026-58502/"}