{"answers":{"affected":"2 open source packages ship an affected version, including guzzlehttp/guzzle.","exploited":"There is no known exploitation of CVE-2026-67339 in the wild and no public exploit code.","fix":"Upgrade guzzlehttp/guzzle to 7.14.2 or later.","what":"CVE-2026-67339 is a medium-severity vulnerability in guzzle, published on 1 Aug 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-67339 and fix it if it is affected.\n\nWhat it is: CVE-2026-67339 is a medium-severity vulnerability in guzzle, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-67339 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- guzzlehttp/guzzle (Packagist): affected all versions; fixed in 7.14.2\n- guzzlehttp/guzzle (Packagist): affected all versions; fixed in 7.14.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-2026-67339/ (Markdown: https://insights.sbomify.com/CVE-2026-67339/index.md)","id":"CVE-2026-67339","markdown":"https://insights.sbomify.com/CVE-2026-67339/index.md","name":"CVE-2026-67339","record":{"aliases":["DEBIAN-CVE-2026-67339","GHSA-94pj-82f3-465w","MINI-7xqg-x9f6-3577","MINI-c626-94jx-5wrm","MINI-c6hq-hvvq-rhx8","MINI-j5pr-65xp-f2f3","MINI-jc25-xfx6-ww7v","MINI-m9qv-6j7v-f482","MINI-p4c6-x32r-8vq8","MINI-xrh5-mpfx-wg2j","UBUNTU-CVE-2026-67339"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP HTTP client library","requires_auth":"none","summary":"Attackers can capture proxy credentials via origin server logs due to improper header isolation in Guzzle HTTP client.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"guzzlehttp/guzzle versions before 7.14.2 fail to properly isolate Proxy-Authorization headers from origin servers in cURL handlers. Attackers can capture proxy credentials through origin server access logs when requests are redirected, bypassed, or sent through SOCKS proxies that Guzzle misclassifies as direct connections.","ecosystems":["Packagist"],"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":"guzzlehttp/guzzle before 7.14.2 Proxy-Authorization Header Disclosure","id":"CVE-2026-67339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"ArcadeDB before 26.7.2 Remote Code Execution via Trigger Scripts","id":"CVE-2026-67340"},"packages":[{"ecosystem":"Packagist","fixed":["7.14.2"],"introduced":["0"],"last_affected":[],"package":"guzzlehttp/guzzle","purl":null,"source":"GHSA-94pj-82f3-465w"},{"ecosystem":"Packagist","fixed":["7.14.2"],"introduced":["0"],"last_affected":[],"package":"guzzlehttp/guzzle","purl":"pkg:composer/guzzlehttp/guzzle","source":"GHSA-94pj-82f3-465w"}],"prev":{"headline":"JupyterLab before 4.5.9 Stored XSS via Extension Manager","id":"CVE-2026-67338"},"products":["guzzle"],"published":"2026-08-01","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["guzzle"]},"summary":"Attackers can capture proxy credentials via origin server logs due to improper header isolation in Guzzle HTTP client.","url":"https://insights.sbomify.com/CVE-2026-67339/"}