{"answers":{"affected":"1 open source package ship an affected version, including ash_authentication_oauth2_server.","exploited":"There is no known exploitation of CVE-2026-82754 in the wild and no public exploit code.","fix":"Upgrade ash_authentication_oauth2_server to 0.3.1 or later.","what":"CVE-2026-82754 is a medium-severity vulnerability in ash-project ash_authentication_oauth2_server, published on 7 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-82754 and fix it if it is affected.\n\nWhat it is: CVE-2026-82754 is a medium-severity vulnerability in ash-project ash_authentication_oauth2_server, published on 7 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-82754 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash_authentication_oauth2_server (Hex): affected from 0.1.0; fixed in 0.3.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-82754/ (Markdown: https://insights.sbomify.com/CVE-2026-82754/index.md)","id":"CVE-2026-82754","markdown":"https://insights.sbomify.com/CVE-2026-82754/index.md","name":"CVE-2026-82754","record":{"aliases":["EEF-CVE-2026-82754","GHSA-wwxg-h779-3wf4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir OAuth2 library","requires_auth":"none","summary":"Attackers can bypass WAF rules and rate limits by accessing OAuth endpoints via /.well-known aliases instead of /oauth paths.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-424","name":"Improper Protection of Alternate Path"}],"description":"Improper Protection of Alternate Path vulnerability in ash-project ash_authentication_oauth2_server exposes the state-changing OAuth endpoints under an unintended URL prefix, bypassing controls scoped to the canonical prefix.\n\noauth2_server_protocol_routes/1 in AshAuthentication.Phoenix.Oauth2Server.Router forwards the same ProtocolRouter at both the /oauth prefix and the /.well-known prefix. Phoenix forward strips the matched prefix before dispatch, so the full route table answers under both mounts, and POST /register, POST /token, and POST /revoke are reachable as /.well-known/register, /.well-known/token, and /.well-known/revoke. Edge controls such as WAF rules, rate limits, or authentication exemptions written against the /oauth paths, or that allow-list /.well-known as unauthenticated, do not apply to the alias.\n\nThis issue affects ash_authentication_oauth2_server: from 0.1.0 before 0.3.1.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ash_authentication_oauth2_server aliases every protocol endpoint under /.well-known, bypassing path-scoped controls","id":"CVE-2026-82754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Information disclosure in ash authentication oauth2 server","id":"CVE-2026-82755"},"packages":[{"ecosystem":"Hex","fixed":["0.3.1"],"introduced":["0.1.0"],"last_affected":[],"package":"ash_authentication_oauth2_server","purl":"pkg:hex/ash_authentication_oauth2_server","source":"EEF-CVE-2026-82754"}],"prev":{"headline":"Denial of service in ash authentication oauth2 server","id":"CVE-2026-82753"},"products":["ash_authentication_oauth2_server"],"published":"2026-09-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["ash-project"]},"summary":"Attackers can bypass WAF rules and rate limits by accessing OAuth endpoints via /.well-known aliases instead of /oauth paths.","url":"https://insights.sbomify.com/CVE-2026-82754/"}