{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56739 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56739 is a high-severity server-side request forgery vulnerability in logto-io logto, published on 24 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56739 and fix it if it is affected.\n\nWhat it is: CVE-2026-56739 is a high-severity server-side request forgery vulnerability in logto-io logto, published on 24 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56739 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-56739/ (Markdown: https://insights.sbomify.com/CVE-2026-56739/index.md)","id":"CVE-2026-56739","markdown":"https://insights.sbomify.com/CVE-2026-56739/index.md","name":"CVE-2026-56739","record":{"aliases":["GHSA-3556-624q-c5w3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Logto auth infrastructure","requires_auth":"high_privilege","summary":"Administrators can trigger Server-Side Request Forgery via webhooks or OAuth connectors, potentially exposing internal data or credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.43.0, Logto fetches administrator-controlled outbound destinations without validating the address used for the connection. Webhook delivery in packages/core/src/libraries/hook/utils.ts can reach special-use and cloud metadata addresses. Custom OAuth2 connectors can use an attacker-selected userInfoEndpoint and forward the OAuth access token in the Authorization header, while OIDC connectors can fetch an attacker-selected jwksUri. The affected operations require tenant administrative configuration access, but they cross the server's network boundary and can expose internal data or upstream provider credentials. This issue is fixed in version 1.43.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: SSRF via Webhooks and Custom OAuth2 Connector UserInfo Endpoint","id":"CVE-2026-56739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"JLine: Unauthenticated Remote Memory Exhaustion via Unbounded Telnet NEW-ENVIRON Variables","id":"CVE-2026-56740"},"packages":[],"prev":{"headline":"phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion","id":"CVE-2026-56738"},"products":["logto"],"published":"2026-09-24","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-09-28","vendors":["logto-io"]},"summary":"Administrators can trigger Server-Side Request Forgery via webhooks or OAuth connectors, potentially exposing internal data or credentials.","url":"https://insights.sbomify.com/CVE-2026-56739/"}