{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-16117 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-16117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-16117 is a critical path traversal vulnerability in @fastify/http-proxy, published on 18 Jul 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-16117 and fix it if it is affected.\n\nWhat it is: CVE-2026-16117 is a critical path traversal vulnerability in @fastify/http-proxy, published on 18 Jul 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-16117 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-16117/ (Markdown: https://insights.sbomify.com/CVE-2026-16117/index.md)","id":"CVE-2026-16117","markdown":"https://insights.sbomify.com/CVE-2026-16117/index.md","name":"CVE-2026-16117","record":{"aliases":["GHSA-mx7v-qhg9-2mvv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fastify HTTP proxy","requires_auth":"none","summary":"Attackers can bypass prefix rewriting to access hidden upstream paths, including administrative endpoints, by using URL-encoded characters in requests.","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":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Impact: @fastify/http-proxy versions up to and including 11.5.0 fail to rewrite the request prefix when the prefix segment is URL-encoded. Fastify's router URL-decodes paths for route matching, but request.url retains the original encoded form, and the prefix-rewrite step uses a literal string replace against the decoded prefix. A request that encodes one or more characters of the configured prefix therefore matches the route but skips the rewrite, so the raw encoded path is forwarded to the upstream unchanged. The upstream then decodes the path and serves it, letting an attacker reach upstream paths that the proxy was configured to hide via rewritePrefix, including internal or administrative endpoints.\n\nPatches: upgrade to @fastify/http-proxy 11.6.0.\n\nWorkarounds: none.","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 URL-encoded characters","id":"CVE-2026-16117","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":"Xdgmime: heap-based buffer overflow in _xdg_mime_magic_parse_magic_line() in xdgmimemagic.c","id":"CVE-2026-16118"},"packages":[],"prev":{"headline":"IBM DataPower Gateway Type Confusion","id":"CVE-2026-16111"},"products":["@fastify/http-proxy"],"published":"2026-07-18","related":[{"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"},{"cvss_score":7.5,"headline":"@fastify/http-proxy vulnerable to prefix escape via backslash dot-segments","id":"CVE-2026-85124","kev_date_added":null,"published":"2026-09-03"}],"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":"total"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["@fastify/http-proxy"]},"summary":"Attackers can bypass prefix rewriting to access hidden upstream paths, including administrative endpoints, by using URL-encoded characters in requests.","url":"https://insights.sbomify.com/CVE-2026-16117/"}