# CVE-2026-63088: stoatchat < 0.14.0 SSRF via DNS-based IP Blocklist Bypass

> Unauthenticated attackers can bypass IP blocklists to perform server-side request forgery, potentially accessing internal resources.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026

## What is CVE-2026-63088?

CVE-2026-63088 is a high-severity server-side request forgery vulnerability in stoatchat, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

stoatchat before 0.14.0 contains a server-side request forgery (SSRF) vulnerability that allows unauthenticated network-accessible attackers to bypass the DNS-based IP blocklist by exploiting incomplete address validation in the url_is_blacklisted function, which inspects only the first resolved address while the underlying HTTP client iterates all cached addresses.

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

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


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

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

## Is CVE-2026-63088 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63088 is a high-severity server-side request forgery vulnerability in stoatchat, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63088 exists.

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

## Sources

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

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