Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/logto-io/logto/commit/16f4b2e732d5114ac98646c9370ec6ab61d6ed2
- https://github.com/logto-io/logto/pull/9501
- https://github.com/logto-io/logto/releases/tag/v1.43.0
- https://github.com/logto-io/logto/security/advisories/GHSA-3556-624q-c5w3
FAQ
What is CVE-2026-56739?
CVE-2026-56739 is a documented vulnerability. 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 con...
How severe is CVE-2026-56739?
CVSS scoring is not yet available for CVE-2026-56739. Check NVD for updates.
Is there a patch for CVE-2026-56739?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.