{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:git-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-57282 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:git-client to 6.6.1 or later.","what":"CVE-2026-57282 is a medium-severity command injection vulnerability in Jenkins Git client Plugin, published on 24 Jun 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-57282 and fix it if it is affected.\n\nWhat it is: CVE-2026-57282 is a medium-severity command injection vulnerability in Jenkins Git client Plugin, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-57282 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:git-client (Maven): affected all versions; fixed in 6.6.1\n- org.jenkins-ci.plugins:git-client (Maven): affected all versions; fixed in 6.6.1\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-57282/ (Markdown: https://insights.sbomify.com/CVE-2026-57282/index.md)","id":"CVE-2026-57282","markdown":"https://insights.sbomify.com/CVE-2026-57282/index.md","name":"CVE-2026-57282","record":{"aliases":["GHSA-wp5x-hrrw-6r4g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Git client Plugin","requires_auth":"low_privilege","summary":"Attackers controlling build directory names can execute arbitrary OS commands on Jenkins agents via improper escaping in the Git client Plugin.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"git_client","vendor":"jenkins"}],"cvss":{"score":5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Jenkins Git client Plugin 6.6.0 and earlier does not correctly escape the workspace directory name when it is embedded into a generated SSH wrapper script, allowing attackers able to control the name of a build's working directory to execute arbitrary operating system commands on the agent.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins Git client Plugin has an OS command injection vulnerability on agents","id":"CVE-2026-57282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Pipeline: Groovy Plugin has a CSRF vulnerability","id":"CVE-2026-57283"},"packages":[{"ecosystem":"Maven","fixed":["6.6.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:git-client","purl":null,"source":"GHSA-wp5x-hrrw-6r4g"},{"ecosystem":"Maven","fixed":["6.6.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:git-client","purl":"pkg:maven/org.jenkins-ci.plugins/git-client","source":"GHSA-wp5x-hrrw-6r4g"}],"prev":{"headline":"Jenkins Script Security Plugin has a script security bypass vulnerability","id":"CVE-2026-57281"},"products":["Jenkins Git client Plugin"],"published":"2026-06-24","related":[{"cvss_score":8.8,"headline":"Improper Neutralization of Special Elements used in an OS Command in Jenkins Git Client Plugin","id":"CVE-2019-10392","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":8.1,"headline":"Jenkins Git client plugin 3.11.0 does not perform SSH host key verification","id":"CVE-2022-36881","kev_date_added":null,"published":"2022-07-27"},{"cvss_score":5,"headline":"Jenkins Git client Plugin has an OS command injection vulnerability on agents in Git client Plugin","id":"CVE-2025-67640","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":4.3,"headline":"Jenkins Git client Plugin file system information disclosure vulnerability","id":"CVE-2025-58458","kev_date_added":null,"published":"2025-09-03"},{"cvss_score":3.3,"headline":"Insecure temporary file usage in Jenkins Git Client Plugin","id":"CVE-2017-1000242","kev_date_added":null,"published":"2017-11-01"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["Jenkins Project"]},"summary":"Attackers controlling build directory names can execute arbitrary OS commands on Jenkins agents via improper escaping in the Git client Plugin.","url":"https://insights.sbomify.com/CVE-2026-57282/"}