{"answers":{"affected":"5 open source packages ship an affected version, including github.com/oauth2-proxy/oauth2-proxy/v7, oauth2-proxy and github.com/oauth2-proxy/oauth2-proxy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34454 in the wild and no public exploit code.","fix":"Upgrade github.com/oauth2-proxy/oauth2-proxy/v7 to 7.15.2 or later.","what":"CVE-2026-34454 is a low-severity authentication bypass vulnerability in oauth2-proxy, published on 14 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34454 and fix it if it is affected.\n\nWhat it is: CVE-2026-34454 is a low-severity authentication bypass vulnerability in oauth2-proxy, published on 14 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34454 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/oauth2-proxy/oauth2-proxy/v7 (Go): affected from 7.11.0; fixed in 7.15.2\n- github.com/oauth2-proxy/oauth2-proxy/v7 (Go): affected from 7.11.0; fixed in 7.15.2\n- github.com/oauth2-proxy/oauth2-proxy/v7 (Go): affected from 7.11.0; fixed in 7.15.2\n- oauth2-proxy (Bitnami): affected from 7.11.0; fixed in 7.15.2\n- github.com/oauth2-proxy/oauth2-proxy (Go): affected all versions; no fix listed\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-34454/ (Markdown: https://insights.sbomify.com/CVE-2026-34454/index.md)","id":"CVE-2026-34454","markdown":"https://insights.sbomify.com/CVE-2026-34454/index.md","name":"CVE-2026-34454","record":{"aliases":["BIT-oauth2-proxy-2026-34454","GHSA-f24x-5g9q-753f","GO-2026-5341","MINI-m8xg-wgh8-86m2","MINI-wcv9-4mcj-w659"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"OAuth2 reverse proxy","requires_auth":"none","summary":"Attackers on shared devices can hijack sessions because the proxy fails to clear cookies during sign-in page rendering, requiring specific logout flow configurations.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"oauth2_proxy","vendor":"oauth2_proxy_project"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"},{"id":"CWE-384","name":"Session Fixation"}],"description":"OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. A regression introduced in 7.11.0 prevents OAuth2 Proxy from clearing the session cookie when rendering the sign-in page. In deployments that rely on the sign-in page as part of their logout flow, a user may be shown the sign-in page while the existing session cookie remains valid, meaning the browser session is not actually logged out. On shared workstations or devices, a subsequent user could continue to use the previous user's authenticated session. Deployments that use a dedicated logout/sign-out endpoint to terminate sessions are not affected. This issue is fixed in 7.15.2","ecosystems":["Bitnami","Go"],"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":"OAuth2 Proxy: Session cookie not cleared when rendering sign-in page","id":"CVE-2026-34454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":5,"n_references":2,"next":{"headline":"Hi.Events: SQL Injection via Unvalidated sort_by Query Parameter in Multiple Repository Classes","id":"CVE-2026-34455"},"packages":[{"ecosystem":"Bitnami","fixed":["7.15.2"],"introduced":["7.11.0"],"last_affected":[],"package":"oauth2-proxy","purl":"pkg:bitnami/oauth2-proxy","source":"BIT-oauth2-proxy-2026-34454"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/oauth2-proxy/oauth2-proxy","purl":"pkg:golang/github.com/oauth2-proxy/oauth2-proxy","source":"GO-2026-5341"},{"ecosystem":"Go","fixed":["7.15.2"],"introduced":["7.11.0"],"last_affected":[],"package":"github.com/oauth2-proxy/oauth2-proxy/v7","purl":null,"source":"GHSA-f24x-5g9q-753f"},{"ecosystem":"Go","fixed":["7.15.2"],"introduced":["7.11.0"],"last_affected":[],"package":"github.com/oauth2-proxy/oauth2-proxy/v7","purl":"pkg:golang/github.com/oauth2-proxy/oauth2-proxy/v7","source":"GHSA-f24x-5g9q-753f"},{"ecosystem":"Go","fixed":["7.15.2"],"introduced":["7.11.0"],"last_affected":[],"package":"github.com/oauth2-proxy/oauth2-proxy/v7","purl":"pkg:golang/github.com/oauth2-proxy/oauth2-proxy/v7","source":"GO-2026-5341"}],"prev":{"headline":"SiYuan: Unauthenticated Access to Password-Protected Bookmarks via /api/bookmark/getBookmark","id":"CVE-2026-34453"},"products":["oauth2-proxy"],"published":"2026-04-14","related":[{"cvss_score":9.1,"headline":"OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing","id":"CVE-2026-40575","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":9.1,"headline":"OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode","id":"CVE-2026-34457","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":9.1,"headline":"OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion","id":"CVE-2025-54576","kev_date_added":null,"published":"2025-07-30"},{"cvss_score":8.8,"headline":"Cross-site Request Forgery (CSRF)","id":"CVE-2017-1000069","kev_date_added":null,"published":"2017-07-13"},{"cvss_score":8.2,"headline":"OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex","id":"CVE-2026-41059","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":7.1,"headline":"Open Redirect in OAuth2 Proxy","id":"CVE-2020-11053","kev_date_added":null,"published":"2020-05-07"},{"cvss_score":6.8,"headline":"OAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@ Email Claims","id":"CVE-2026-40574","kev_date_added":null,"published":"2026-04-21"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["oauth2-proxy"]},"summary":"Attackers on shared devices can hijack sessions because the proxy fails to clear cookies during sign-in page rendering, requiring specific logout flow configurations.","url":"https://insights.sbomify.com/CVE-2026-34454/"}