{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54714 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54714 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54714 is a medium-severity cross-site scripting vulnerability in logto-io logto, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54714 and fix it if it is affected.\n\nWhat it is: CVE-2026-54714 is a medium-severity cross-site scripting vulnerability in logto-io logto, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-54714 in the wild and no public exploit code.\n\nAffected product: logto-io logto. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-54714/ (Markdown: https://insights.sbomify.com/CVE-2026-54714/index.md)","id":"CVE-2026-54714","markdown":"https://insights.sbomify.com/CVE-2026-54714/index.md","name":"CVE-2026-54714","record":{"aliases":["GHSA-cpm5-w86q-w85f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Logto auth infrastructure","requires_auth":"none","summary":"Attackers can inject scripts via unescaped SAML RelayState parameters, executing code on the Logto tenant origin after user login.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, @logto/core reflected the SAML RelayState, SAMLResponse, and actionUrl into a Logto-origin auto-submit HTML form in packages/core/src/saml-application/SamlApplication/utils.ts without HTML-attribute escaping. A SAML application flow with a crafted RelayState from GET or POST /api/saml/:id/authn could inject script that runs on the Logto tenant origin after the user completes login. This issue is fixed in version 1.41.0.","ecosystems":[],"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":"Logto: XSS via unescaped RelayState in SAML auto-submit form","id":"CVE-2026-54714","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"GoAccess: Heap Out-of-Bounds Write in parse_browser()","id":"CVE-2026-54715"},"packages":[],"prev":{"headline":"CakePHP Queue: Incomplete Comparison in getUniqueId vulnerable to collisions","id":"CVE-2026-54713"},"products":["logto"],"published":"2026-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-07-13","vendors":["logto-io"]},"summary":"Attackers can inject scripts via unescaped SAML RelayState parameters, executing code on the Logto tenant origin after user login.","url":"https://insights.sbomify.com/CVE-2026-54714/"}