{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-18174 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18174 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18174 is a medium-severity vulnerability in @fastify/forwarded, published on 29 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-18174 and fix it if it is affected.\n\nWhat it is: CVE-2026-18174 is a medium-severity vulnerability in @fastify/forwarded, published on 29 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-18174 in the wild and no public exploit code.\n\nAffected product: @fastify/forwarded. 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-18174/ (Markdown: https://insights.sbomify.com/CVE-2026-18174/index.md)","id":"CVE-2026-18174","markdown":"https://insights.sbomify.com/CVE-2026-18174/index.md","name":"CVE-2026-18174","record":{"aliases":["GHSA-2849-m2w7-xm8f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fastify forwarded library","requires_auth":"none","summary":"Attackers can bypass IP-based security controls like allowlists or rate limits by injecting tab characters into the X-Forwarded-For header.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openjs","cpe":[{"product":"fastify\\/forwarded","vendor":"fastify"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"@fastify/forwarded resolves client addresses from the X-Forwarded-For header. In versions before 3.0.2, when the header contains two or more comma separated entries, the parser trims only space characters and does not strip horizontal tabs, even though RFC 7230 defines optional whitespace as both space and tab. As a result, an entry padded with a tab keeps the literal tab in the resolved address string. Applications that make exact string match security decisions on the resolved client IP, such as an allowlist, a blocklist, a per IP rate limit key, or audit log correlation, can be evaded because the tab corrupted string no longer matches the expected value. This does not cross the trust boundary, since a tab corrupted string is not a valid IP and cannot be mistaken for a trusted proxy. The issue is fixed in @fastify/forwarded 3.0.2.","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/forwarded vulnerable to improper input validation via unstripped tab characters in X-Forwarded-For","id":"CVE-2026-18174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"IBM i is Affected By Improper Authorization and Authentication Vulnerabilities in DDM / DRDA [, ]","id":"CVE-2026-18175"},"packages":[],"prev":{"headline":"IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities","id":"CVE-2026-18173"},"products":["@fastify/forwarded"],"published":"2026-07-29","related":[],"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-07-29","vendors":["@fastify/forwarded"]},"summary":"Attackers can bypass IP-based security controls like allowlists or rate limits by injecting tab characters into the X-Forwarded-For header.","url":"https://insights.sbomify.com/CVE-2026-18174/"}