{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-18427 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18427 is a high-severity path traversal vulnerability in @fastify/static, published on 6 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-18427 and fix it if it is affected.\n\nWhat it is: CVE-2026-18427 is a high-severity path traversal vulnerability in @fastify/static, published on 6 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-18427 in the wild and no public exploit code.\n\nAffected product: @fastify/static. 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-18427/ (Markdown: https://insights.sbomify.com/CVE-2026-18427/index.md)","id":"CVE-2026-18427","markdown":"https://insights.sbomify.com/CVE-2026-18427/index.md","name":"CVE-2026-18427","record":{"aliases":["GHSA-423g-23ch-w7c6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Fastify static file plugin","requires_auth":"none","summary":"An attacker can bypass route guards to read protected static files by using non-canonical path segments in requests to the Fastify static plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openjs","cpe":[{"product":"fastify-static","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-436","name":"Interpretation Conflict"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"@fastify/static before version 10.1.3 contains an incomplete fix for a previous route guard bypass. The static file handler rejected only parent directory segments, but it did not canonicalize dot segments, duplicate slashes, encoded dots, or backslashes before route matching and before delegating to the send layer. As a result, an unauthenticated attacker could request a file protected by a route based guard using a non canonical path form that misses the guarded route yet resolves back onto the protected file, disclosing its contents. Applications that protect a subtree of the static root with a route based guard are affected, while applications relying on the allowedPath option are not. This is fixed in @fastify/static 10.1.3, which canonicalizes the pathname, including rejecting backslashes, on the path used for routing and serving.","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/static vulnerable to route guard bypass via non-canonical path segments","id":"CVE-2026-18427","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":"SQL Query Validation Bypass in OpenSearch Direct Query","id":"CVE-2026-18428"},"packages":[],"prev":{"headline":"Missing authorization in Concrete CMS","id":"CVE-2026-18426"},"products":["@fastify/static"],"published":"2026-08-06","related":[{"cvss_score":8.8,"headline":"DOS and Open Redirect with user input","id":"CVE-2021-22964","kev_date_added":null,"published":"2021-10-14"},{"cvss_score":7.5,"headline":"@fastify/static vulnerable to route guard bypass via path traversal","id":"CVE-2026-15074","kev_date_added":null,"published":"2026-07-23"},{"cvss_score":6.1,"headline":"URL Redirection to Untrusted Site ('Open Redirect') in fastify-static","id":"CVE-2021-22963","kev_date_added":null,"published":"2021-10-14"},{"cvss_score":5.9,"headline":"@fastify/static vulnerable to route guard bypass via encoded path separators","id":"CVE-2026-6414","kev_date_added":null,"published":"2026-04-16"},{"cvss_score":5.3,"headline":"@fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths","id":"CVE-2026-7120","kev_date_added":null,"published":"2026-07-23"},{"cvss_score":5.3,"headline":"@fastify/static vulnerable to path traversal in directory listing","id":"CVE-2026-6410","kev_date_added":null,"published":"2026-04-16"}],"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-08-06","vendors":["@fastify/static"]},"summary":"An attacker can bypass route guards to read protected static files by using non-canonical path segments in requests to the Fastify static plugin.","url":"https://insights.sbomify.com/CVE-2026-18427/"}