{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-85124 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85124 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85124 is a high-severity path traversal vulnerability in @fastify/http-proxy, published on 3 Sep 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-85124 and fix it if it is affected.\n\nWhat it is: CVE-2026-85124 is a high-severity path traversal vulnerability in @fastify/http-proxy, published on 3 Sep 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-85124 in the wild and no public exploit code.\n\nAffected product: @fastify/http-proxy. 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-85124/ (Markdown: https://insights.sbomify.com/CVE-2026-85124/index.md)","id":"CVE-2026-85124","markdown":"https://insights.sbomify.com/CVE-2026-85124/index.md","name":"CVE-2026-85124","record":{"aliases":["GHSA-qv33-689p-2xq5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fastify HTTP proxy","requires_auth":"none","summary":"An unauthenticated attacker can bypass proxy prefix restrictions using backslash dot-segments to access hidden internal upstream endpoints.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openjs","cpe":[{"product":"fastify\\/http-proxy","vendor":"fastify"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from library only rejects forward-slash traversal, so a request containing backslash dot-segments can escape the boundary set by the prefix and rewritePrefix options. An unauthenticated network attacker can use this to reach upstream paths that were meant to stay hidden behind the proxy, resulting in disclosure of internal endpoints. This is a path traversal issue (CWE-22). Users should upgrade to @fastify/http-proxy 11.6.2 or later.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"@fastify/http-proxy vulnerable to prefix escape via backslash dot-segments","id":"CVE-2026-85124","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in YAMAP -Social Trekking GPS App","id":"CVE-2026-85125"},"packages":[],"prev":{"headline":"Easy Form Builder 4.0.0 - 4.1.3 - Unauthenticated Registration Policy Bypass via Login Form Type Confusion","id":"CVE-2026-85123"},"products":["@fastify/http-proxy"],"published":"2026-09-03","related":[{"cvss_score":10,"headline":"@fastify/http-proxy vulnerable to prefix escape via URL-encoded characters","id":"CVE-2026-16117","kev_date_added":null,"published":"2026-07-18"},{"cvss_score":9,"headline":"@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers","id":"CVE-2026-33805","kev_date_added":null,"published":"2026-04-15"},{"cvss_score":8.7,"headline":"@fastify/http-proxy vulnerable to prefix escape via WebSocket path traversal","id":"CVE-2026-15631","kev_date_added":null,"published":"2026-07-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-03","vendors":["@fastify/http-proxy"]},"summary":"An unauthenticated attacker can bypass proxy prefix restrictions using backslash dot-segments to access hidden internal upstream endpoints.","url":"https://insights.sbomify.com/CVE-2026-85124/"}