{"answers":{"affected":"2 open source packages ship an affected version, including auth0-js. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42280 in the wild and no public exploit code.","fix":"Upgrade auth0-js to 10.0.0 or later.","what":"CVE-2026-42280 is a high-severity missing authorization vulnerability in auth0.js, published on 27 May 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-42280 and fix it if it is affected.\n\nWhat it is: CVE-2026-42280 is a high-severity missing authorization vulnerability in auth0.js, published on 27 May 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-42280 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- auth0-js (npm): affected from 8.11.0; fixed in 10.0.0\n- auth0-js (npm): affected from 8.11.0; fixed in 10.0.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-42280/ (Markdown: https://insights.sbomify.com/CVE-2026-42280/index.md)","id":"CVE-2026-42280","markdown":"https://insights.sbomify.com/CVE-2026-42280/index.md","name":"CVE-2026-42280","record":{"aliases":["GHSA-8qjv-jj2q-x832"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Auth0 JavaScript SDK","requires_auth":"low_privilege","summary":"Attackers can retrieve user profile information by providing a crafted invalid ID token with a valid access token in the Auth0.js SDK.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"auth0.js","vendor":"auth0"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Auth0.js is a client-side JavaScript library for Auth0. From 8.11.0 to 9.32.0, under specific preconditions, the Auth0.js SDK may improperly return user profile information using a valid access token when a specifically crafted invalid ID token is provided. This vulnerability is fixed in 10.0.0.","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":true,"headline":"Improper Permission Checking in Auth.js SDK","id":"CVE-2026-42280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"MagicMirror²: Unauthenticated SSRF via /cors endpoint","id":"CVE-2026-42281"},"packages":[{"ecosystem":"npm","fixed":["10.0.0"],"introduced":["8.11.0"],"last_affected":[],"package":"auth0-js","purl":null,"source":"GHSA-8qjv-jj2q-x832"},{"ecosystem":"npm","fixed":["10.0.0"],"introduced":["8.11.0"],"last_affected":[],"package":"auth0-js","purl":"pkg:npm/auth0-js","source":"GHSA-8qjv-jj2q-x832"}],"prev":{"headline":"solidtime: Time entry update endpoint allows cross-organization modification of a known time-entry UUID","id":"CVE-2026-42279"},"products":["auth0.js"],"published":"2026-05-27","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-6873","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery (CSRF) in Auth0","id":"CVE-2018-6874","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":8.8,"headline":"Auth0-js bypasses CSRF checks","id":"CVE-2018-7307","kev_date_added":null,"published":"2018-03-06"},{"cvss_score":7.7,"headline":"Authorization header is not sanitized in an error object in auth0","id":"CVE-2020-15125","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":7.5,"headline":"auth0-js Privilege Escalation Vulnerability","id":"CVE-2017-17068","kev_date_added":null,"published":"2017-12-06"},{"cvss_score":5.5,"headline":"Information disclosure through error object","id":"CVE-2020-5263","kev_date_added":null,"published":"2020-04-09"}],"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":"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-05-28","vendors":["auth0"]},"summary":"Attackers can retrieve user profile information by providing a crafted invalid ID token with a valid access token in the Auth0.js SDK.","url":"https://insights.sbomify.com/CVE-2026-42280/"}