{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92395 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92395 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92395 is a critical vulnerability in @fastify/proxy-addr, published on 16 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-92395 and fix it if it is affected.\n\nWhat it is: CVE-2026-92395 is a critical vulnerability in @fastify/proxy-addr, published on 16 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-92395 in the wild and no public exploit code.\n\nAffected product: @fastify/proxy-addr. 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-92395/ (Markdown: https://insights.sbomify.com/CVE-2026-92395/index.md)","id":"CVE-2026-92395","markdown":"https://insights.sbomify.com/CVE-2026-92395/index.md","name":"CVE-2026-92395","record":{"aliases":["GHSA-8cmm-mhw6-v7xq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Fastify proxy plugin","requires_auth":"none","summary":"Attackers can spoof IP addresses by exploiting IPv4-mapped IPv6 trust subnet parsing, bypassing IP-based access controls and rate limiting in Fastify applications.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openjs","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"},{"id":"CWE-348","name":"Use of Less Trusted Source"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"@fastify/proxy-addr is a Fastify plugin that determines a request's client address behind trusted reverse proxies, and it backs Fastify request.ip and request.ips. In versions 3.0.0 through 5.1.0, a trust subnet written in IPv4-mapped IPv6 notation with an IPv4-sized prefix, such as ::ffff:10.0.0.0/8 instead of the correct ::ffff:10.0.0.0/104, is accepted without error but trusts every IPv4 address on the internet rather than the block it names. Because the socket peer then becomes trusted at hop 0, any unauthenticated client can supply an arbitrary X-Forwarded-For header and control the address the application reads, which defeats IP-based access control, rate limiting, geolocation, and audit logging. The plugin inherited this defect from the upstream proxy-addr module (CVE-2026-90711). The issue is fixed in @fastify/proxy-addr 5.1.1, and users should upgrade to 5.1.1 or later. As a workaround, ensure any IPv4-mapped IPv6 trust subnet uses a prefix length of at least 97, or express the range in plain IPv4 notation.","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/proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet","id":"CVE-2026-92395","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":"Ruijie RG-EW3000GX configChange unifyframe-sgi.elf cc_set os command injection","id":"CVE-2026-92397"},"packages":[],"prev":{"headline":"Apache YuniKorn: Admission control bypass via workload UPDATE operation","id":"CVE-2026-92393"},"products":["@fastify/proxy-addr"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-17","vendors":["@fastify/proxy-addr"]},"summary":"Attackers can spoof IP addresses by exploiting IPv4-mapped IPv6 trust subnet parsing, bypassing IP-based access controls and rate limiting in Fastify applications.","url":"https://insights.sbomify.com/CVE-2026-92395/"}