{"answers":{"affected":"2 open source packages ship an affected version, including auth0/symfony.","exploited":"There is no known exploitation of CVE-2026-50157 in the wild and no public exploit code.","fix":"Upgrade auth0/symfony to 5.9.0 or later.","what":"CVE-2026-50157 is a medium-severity vulnerability in auth0 symfony, published on 14 Sep 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-50157 and fix it if it is affected.\n\nWhat it is: CVE-2026-50157 is a medium-severity vulnerability in auth0 symfony, published on 14 Sep 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-50157 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- auth0/symfony (Packagist): affected from 5.0.0-BETA0; fixed in 5.9.0\n- auth0/symfony (Packagist): affected from 5.0.0-BETA0; fixed in 5.9.0\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-50157/ (Markdown: https://insights.sbomify.com/CVE-2026-50157/index.md)","id":"CVE-2026-50157","markdown":"https://insights.sbomify.com/CVE-2026-50157/index.md","name":"CVE-2026-50157","record":{"aliases":["GHSA-ffq7-hh2j-r24p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Auth0 Symfony SDK","requires_auth":"low_privilege","summary":"The Auth0 Symfony SDK accepts bearer tokens via URL query parameters, risking token exposure in logs and history, allowing potential replay attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-598","name":"Use of HTTP Request With Sensitive Query String"}],"description":"Auth0 Symfony is a Symfony SDK for Auth0 Authentication and Management APIs. From 5.0.0-BETA0 until 5.9.0, the Authorizer::authenticate() and Authorizer::supports() paths in the Authorizer security authenticator may accept OAuth 2.0 bearer access tokens from the token URL query parameter as well as the Authorization header for protected HTTP routes. Query-string tokens can be recorded in server logs, browser history, or referrer data and then replayed against protected API endpoints. This issue is fixed in version 5.9.0.","ecosystems":["Packagist"],"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":"Auth0 Symfony: Bearer Token Accepted via URL Query Parameter in Auth0 Symfony SDK","id":"CVE-2026-50157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"yutu: Arbitrary File Write via MCP `caption-download` Tool","id":"CVE-2026-50158"},"packages":[{"ecosystem":"Packagist","fixed":["5.9.0"],"introduced":["5.0.0-BETA0"],"last_affected":[],"package":"auth0/symfony","purl":null,"source":"GHSA-ffq7-hh2j-r24p"},{"ecosystem":"Packagist","fixed":["5.9.0"],"introduced":["5.0.0-BETA0"],"last_affected":[],"package":"auth0/symfony","purl":"pkg:composer/auth0/symfony","source":"GHSA-ffq7-hh2j-r24p"}],"prev":{"headline":"Missing authorization in ceph","id":"CVE-2026-50152"},"products":["symfony"],"published":"2026-09-14","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-09-14","vendors":["auth0"]},"summary":"The Auth0 Symfony SDK accepts bearer tokens via URL query parameters, risking token exposure in logs and history, allowing potential replay attacks.","url":"https://insights.sbomify.com/CVE-2026-50157/"}