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.
CVE-2026-56739
This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(low)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity85% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 24, 2026v1.43.0
Patch available: logto-io/logto v1.43.0
https://github.com/logto-io/logto/releases/tag/v1.43.0commit 16f4b2e732d5 (logto-io/logto)
Patch available: logto-io/logto v1.43.0 (contains commit 16f4b2e732d5)
https://github.com/logto-io/logto/commit/16f4b2e732d5114ac98646c9370ec6ab61d6ed26fix(core,shared): block SSRF in webhook and SSO outbound requests
Patch available: logto-io/logto v1.43.0 (PR #9501 merged 2026-08-27)
https://github.com/logto-io/logto/pull/9501SSRF via Webhooks and Custom OAuth2 Connector UserInfo Endpoint (CWE-918) · Advisory · logto-io/logto · GitHub
https://github.com/logto-io/logto/security/advisories/GHSA-3556-624q-c5w3Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 16:34 UTCEG score recompute
- 2026-09-24 15:32 UTCEG score recompute
- 2026-09-24 15:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-56739?
When was CVE-2026-56739 disclosed?
What is the CVSS score of CVE-2026-56739?
How do I remediate CVE-2026-56739?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56739
Is Your Infrastructure Affected by CVE-2026-56739?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.