{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fatedier/frp. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40910 exists.","fix":"Upgrade github.com/fatedier/frp to 0.68.1 or later.","what":"CVE-2026-40910 is a medium-severity authentication bypass vulnerability in fatedier frp, published on 21 Apr 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-40910 and fix it if it is affected.\n\nWhat it is: CVE-2026-40910 is a medium-severity authentication bypass vulnerability in fatedier frp, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40910 exists.\n\nAffected packages and fixed versions:\n- github.com/fatedier/frp (Go): affected from 0.43.0; fixed in 0.68.1\n- github.com/fatedier/frp (Go): affected from 0.43.0; fixed in 0.68.1\n- github.com/fatedier/frp (Go): affected from 0.43.0; fixed in 0.68.1\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-40910/ (Markdown: https://insights.sbomify.com/CVE-2026-40910/index.md)","id":"CVE-2026-40910","markdown":"https://insights.sbomify.com/CVE-2026-40910/index.md","name":"CVE-2026-40910","record":{"aliases":["GHSA-pq96-pwvg-vrr9","GO-2026-5549"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Reverse proxy tool","requires_auth":"none","summary":"Attackers can bypass authentication in frp HTTP vhost routing when routeByHTTPUser is enabled, accessing protected backends with incorrect credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"frp","vendor":"fatedier"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"frp is a fast reverse proxy. From 0.43.0 to 0.68.0, frp contains an authentication bypass in the HTTP vhost routing path when routeByHTTPUser is used as part of access control. In proxy-style requests, the routing logic uses the username from Proxy-Authorization to select the routeByHTTPUser backend, while the access control check uses credentials from the regular Authorization header. As a result, an attacker who can reach the HTTP vhost entrypoint and knows or can guess the protected routeByHTTPUser value may access a backend protected by httpUser / httpPassword even with an incorrect Proxy-Authorization password. This issue affects deployments that explicitly use routeByHTTPUser. It does not affect ordinary HTTP proxies that do not use this feature. This vulnerability is fixed in 0.68.1.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"frp: Authentication bypass in frp HTTP vhost routing when routeByHTTPUser is used for access control","id":"CVE-2026-40910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks","id":"CVE-2026-40911"},"packages":[{"ecosystem":"Go","fixed":["0.68.1"],"introduced":["0.43.0"],"last_affected":[],"package":"github.com/fatedier/frp","purl":null,"source":"GHSA-pq96-pwvg-vrr9"},{"ecosystem":"Go","fixed":["0.68.1"],"introduced":["0.43.0"],"last_affected":[],"package":"github.com/fatedier/frp","purl":"pkg:golang/github.com/fatedier/frp","source":"GHSA-pq96-pwvg-vrr9"},{"ecosystem":"Go","fixed":["0.68.1"],"introduced":["0.43.0"],"last_affected":[],"package":"github.com/fatedier/frp","purl":"pkg:golang/github.com/fatedier/frp","source":"GO-2026-5549"}],"prev":{"headline":"WWBN AVideo has a Path Traversal in Locale Save Endpoint Enables Arbitrary PHP File Write to Any Web-Accessible Directory (RCE)","id":"CVE-2026-40909"},"products":["frp"],"published":"2026-04-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["fatedier"]},"summary":"Attackers can bypass authentication in frp HTTP vhost routing when routeByHTTPUser is enabled, accessing protected backends with incorrect credentials.","url":"https://insights.sbomify.com/CVE-2026-40910/"}