CVE-2026-56739: logto · Server-Side Request Forgery (SSRF)
Affects logtoSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 1.43.0 soon.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.43.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade logto and logto-io/logto to 1.43.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| logto-iologto | Affected
| Fixed in
|
GitHublogto-io/logtopkg:github/logto-io/logtoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Logto to version 1.43.0 or later, where this SSRF vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by validating outbound request addresses.
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.
References
- github.com/logto-io/logto/security/advisories/GHSA-3556-624q-c5w3 (opens in a new tab)
- github.com/logto-io/logto/pull/9501 (opens in a new tab)
- github.com/logto-io/logto/commit/16f4b2e732d5114ac98646c9370ec6ab61d6ed26 (opens in a new tab)
- github.com/logto-io/logto/releases/tag/v1.43.0 (opens in a new tab)