Private-network data disclosure via unvalidated webhook URL
Published Aug 28, 2026 · Updated Aug 28, 2026
Server-side request forgery in Logto 1.42.0 and earlier allows remote authenticated users to read private-network response bodies. The webhook test handler passes config.url directly to ky.post without address validation, then returns the upstream body in API errors. A tenant administrator with a Management API token can reach it, exposing data from loopback, private-range, or cloud-metadata services.
Summary
What happened
Server-side request forgery in Logto 1.42.0 and earlier allows remote authenticated users to read private-network response bodies. The webhook test handler passes config.url directly to ky.post without address validation, then returns the upstream body in API errors. A tenant administrator with a Management API token can reach it, exposing data from loopback, private-range, or cloud-metadata services.
The record
- CVE
- CVE-2026-82262
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Logto
- Product
- Logto
- Classifications
- CWE-918, T1552.005
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.42.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub Issue #9465 webhook SSRF proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo