{"answers":{"affected":"2 open source packages ship an affected version, including @finos/git-proxy. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54586 exists.","fix":"Upgrade @finos/git-proxy to 1.19.2 or later.","what":"CVE-2025-54586 is a high-severity vulnerability in finos git-proxy, published on 30 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54586 and fix it if it is affected.\n\nWhat it is: CVE-2025-54586 is a high-severity vulnerability in finos git-proxy, published on 30 Jul 2025. 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-2025-54586 exists.\n\nAffected packages and fixed versions:\n- @finos/git-proxy (npm): affected all versions; fixed in 1.19.2\n- @finos/git-proxy (npm): affected all versions; fixed in 1.19.2\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-2025-54586/ (Markdown: https://insights.sbomify.com/CVE-2025-54586/index.md)","id":"CVE-2025-54586","markdown":"https://insights.sbomify.com/CVE-2025-54586/index.md","name":"CVE-2025-54586","record":{"aliases":["GHSA-v98g-8rqx-g93g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Git proxy server","requires_auth":"low_privilege","summary":"Attackers can inject hidden commits into GitProxy to exfiltrate sensitive data without leaving traces in the visible repository history.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gitproxy","vendor":"finos"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"GitProxy is an application that stands between developers and a Git remote endpoint. In versions 1.19.1 and below,   attackers can inject extra commits into the pack sent to GitHub, commits that aren’t pointed to by any branch. Although these “hidden” commits never show up in the repository’s visible history, GitHub still serves them at their direct commit URLs. This lets an attacker exfiltrate sensitive data without ever leaving a trace in the branch view. We rate this a High‑impact vulnerability because it completely compromises repository confidentiality. This is fixed in version 1.19.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"GitProxy is susceptible to a hidden commits injection attack","id":"CVE-2025-54586","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":4,"next":{"headline":"Envoy: Race condition in Dynamic Forward Proxy leads to use-after-free and segmentation faults","id":"CVE-2025-54588"},"packages":[{"ecosystem":"npm","fixed":["1.19.2"],"introduced":["0"],"last_affected":[],"package":"@finos/git-proxy","purl":null,"source":"GHSA-v98g-8rqx-g93g"},{"ecosystem":"npm","fixed":["1.19.2"],"introduced":["0"],"last_affected":[],"package":"@finos/git-proxy","purl":"pkg:npm/%40finos/git-proxy","source":"GHSA-v98g-8rqx-g93g"}],"prev":{"headline":"GitProxy is vulnerable to a new branch approval exploit","id":"CVE-2025-54585"},"products":["git-proxy"],"published":"2025-07-30","related":[{"cvss_score":8.3,"headline":"GitProxy bypasses approvals when pushing multiple branches","id":"CVE-2025-54583","kev_date_added":null,"published":"2025-07-30"},{"cvss_score":8.2,"headline":"GitProxy is vulnerable to a new branch approval exploit","id":"CVE-2025-54585","kev_date_added":null,"published":"2025-07-30"},{"cvss_score":7,"headline":"GitProxy is vulnerable to a packfile parsing exploit","id":"CVE-2025-54584","kev_date_added":null,"published":"2025-07-30"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-31","vendors":["finos"]},"summary":"Attackers can inject hidden commits into GitProxy to exfiltrate sensitive data without leaving traces in the visible repository history.","url":"https://insights.sbomify.com/CVE-2025-54586/"}