Authenticated SSRF via unchecked provider URL joining
Published Jul 12, 2026 · Updated Jul 12, 2026
SSRF in Helicone AI Gateway 0.2.0-beta.0 through 0.2.0-beta.30 allows remote authenticated users to reach internal services. The build_target_url function passes the user-controlled extracted_path_and_query value to Url::join without rejecting input that changes the provider destination. Low-privilege API access and gateway egress are required; successful requests can read cloud metadata or probe internal network services.
Summary
What happened
SSRF in Helicone AI Gateway 0.2.0-beta.0 through 0.2.0-beta.30 allows remote authenticated users to reach internal services. The build_target_url function passes the user-controlled extracted_path_and_query value to Url::join without rejecting input that changes the provider destination. Low-privilege API access and gateway egress are required; successful requests can read cloud metadata or probe internal network services.
The record
- CVE
- CVE-2026-15508
- Published
- Jul 12, 2026
- Updated
- Jul 12, 2026
- Vendor
- Helicone
- Product
- Helicone AI Gateway
- Classifications
- CWE-918, T1552.005, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2026CVE publishedPublication date reported by the CVE source.
- Jul 12, 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.2.0-beta.0
- Affected versionversion=0.2.0-beta.1
- Affected versionversion=0.2.0-beta.10
- Affected versionversion=0.2.0-beta.11
- Affected versionversion=0.2.0-beta.12
- Affected versionversion=0.2.0-beta.13
- Affected versionversion=0.2.0-beta.14
- Affected versionversion=0.2.0-beta.15
- Affected versionversion=0.2.0-beta.16
- Affected versionversion=0.2.0-beta.17
- Affected versionversion=0.2.0-beta.18
- Affected versionversion=0.2.0-beta.19
- Affected versionversion=0.2.0-beta.2
- Affected versionversion=0.2.0-beta.20
- Affected versionversion=0.2.0-beta.21
- Affected versionversion=0.2.0-beta.22
- Affected versionversion=0.2.0-beta.23
- Affected versionversion=0.2.0-beta.24
- Affected versionversion=0.2.0-beta.25
- Affected versionversion=0.2.0-beta.26
- Affected versionversion=0.2.0-beta.27
- Affected versionversion=0.2.0-beta.28
- Affected versionversion=0.2.0-beta.29
- Affected versionversion=0.2.0-beta.3
- Affected versionversion=0.2.0-beta.30
- Affected versionversion=0.2.0-beta.4
- Affected versionversion=0.2.0-beta.5
- Affected versionversion=0.2.0-beta.6
- Affected versionversion=0.2.0-beta.7
- Affected versionversion=0.2.0-beta.8
- Affected versionversion=0.2.0-beta.9
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
- Authenticated provider-destination SSRF proof of conceptproof of concept · unverified
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