# CVE-2026-15508: Helicone ai-gateway AWS Metadata Service service.rs build_target_url server-side request forgery

> Remote attackers can exploit a flaw in Helicone ai-gateway to perform server-side request forgery, potentially accessing internal AWS metadata services.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-9fxj-mchq-843p

## What is CVE-2026-15508?

CVE-2026-15508 is a medium-severity server-side request forgery vulnerability in Helicone ai-gateway, published on 12 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in Helicone ai-gateway up to 0.2.0-beta.30. This affects the function build_target_url of the file ai-gateway/src/dispatcher/service.rs of the component AWS Metadata Service. Executing a manipulation of the argument extracted_path_and_query can lead to server-side request forgery. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-15508?


## How do I fix CVE-2026-15508?

No fix has been published for CVE-2026-15508 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15508 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15508 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15508 and fix it if it is affected.

What it is: CVE-2026-15508 is a medium-severity server-side request forgery vulnerability in Helicone ai-gateway, published on 12 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15508 exists.

Affected product: Helicone ai-gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15508/ (Markdown: https://insights.sbomify.com/CVE-2026-15508/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15508
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15508
- OSV: https://osv.dev/vulnerability/CVE-2026-15508

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15508/
Summaries are generated and may contain mistakes; the official description above is the record.