# CVE-2026-108602: Helicone through v2025.08.21-1 SSRF via Jawn Webhook Sender DNS Resolution

> Authenticated users can exploit DNS rebinding in Helicone's webhook sender to access internal services via SSRF.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 10 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-ch5j-5g34-4wwh

## What is CVE-2026-108602?

CVE-2026-108602 is a medium-severity server-side request forgery vulnerability in helicone, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Helicone through v2025.08.21-1 contains a server-side request forgery vulnerability in the Jawn webhook sender that allows authenticated organization users to reach internal services by using hostnames resolving to private addresses. Attackers can create webhooks with public hostnames that resolve or DNS-rebind to loopback or internal addresses, causing blind POST requests to internal HTTPS services.

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

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


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

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

## Is CVE-2026-108602 being exploited?

There is no known exploitation of CVE-2026-108602 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108602 is a medium-severity server-side request forgery vulnerability in helicone, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108602 in the wild and no public exploit code.

Affected product: helicone. 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-108602/ (Markdown: https://insights.sbomify.com/CVE-2026-108602/index.md)
```

## Sources

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

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