{"answers":{"affected":"2 open source packages ship an affected version, including @better-auth/oauth-provider.","exploited":"There is no known exploitation of CVE-2026-67332 in the wild and no public exploit code.","fix":"Upgrade @better-auth/oauth-provider to 1.7.0-beta.4 or later.","what":"CVE-2026-67332 is a medium-severity authentication bypass vulnerability in better-auth oauth-provider, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67332 and fix it if it is affected.\n\nWhat it is: CVE-2026-67332 is a medium-severity authentication bypass vulnerability in better-auth oauth-provider, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-67332 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @better-auth/oauth-provider (npm): affected from 1.4.8; fixed in 1.7.0-beta.4\n- @better-auth/oauth-provider (npm): affected from 1.4.8; fixed in 1.7.0-beta.4\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-67332/ (Markdown: https://insights.sbomify.com/CVE-2026-67332/index.md)","id":"CVE-2026-67332","markdown":"https://insights.sbomify.com/CVE-2026-67332/index.md","name":"CVE-2026-67332","record":{"aliases":["GHSA-hq9c-fvm2-pfh9","GHSA-p2fr-6hmx-4528"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OAuth provider library","requires_auth":"low_privilege","summary":"Attackers can obtain access tokens for unauthorized resources by bypassing audience binding in the OAuth flow.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"@better-auth/oauth-provider before 1.7.0-beta.4 fails to bind access-token audience to the authorization grant, allowing clients to request tokens for unrelated resources. Attackers can complete an OAuth flow and obtain access tokens whose audience targets resource servers the authorization never covered, bypassing intended authorization boundaries.","ecosystems":["npm"],"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":"@better-auth/oauth-provider before 1.7.0-beta.4 Authorization Bypass","id":"CVE-2026-67332","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"better-auth before 1.6.13 Stored XSS via javascript redirect_uri","id":"CVE-2026-67333"},"packages":[{"ecosystem":"npm","fixed":["1.7.0-beta.4"],"introduced":["1.4.8"],"last_affected":[],"package":"@better-auth/oauth-provider","purl":null,"source":"GHSA-p2fr-6hmx-4528"},{"ecosystem":"npm","fixed":["1.7.0-beta.4"],"introduced":["1.4.8"],"last_affected":[],"package":"@better-auth/oauth-provider","purl":"pkg:npm/%40better-auth/oauth-provider","source":"GHSA-p2fr-6hmx-4528"}],"prev":{"headline":"better-auth SCIM 1.5.0 before 1.7.0-beta.4 Authorization Bypass","id":"CVE-2026-67331"},"products":["oauth-provider"],"published":"2026-08-01","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":"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-10-08","vendors":["better-auth"]},"summary":"Attackers can obtain access tokens for unauthorized resources by bypassing audience binding in the OAuth flow.","url":"https://insights.sbomify.com/CVE-2026-67332/"}