# CVE-2026-73058: stoatchat before 0.15.0 SSRF via IPv6 unspecified address bypass

> Unauthenticated attackers can bypass SSRF protections using IPv6 unspecified addresses to access internal services and retrieve sensitive data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/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 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-4rmr-77qv-hq47, GHSA-6x44-jq26-vpv6

## What is CVE-2026-73058?

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

### Official description

stoatchat versions before 0.15.0 fail to block the IPv6 unspecified address (::) in the SSRF blocklist, allowing unauthenticated attackers to bypass protections via the /proxy and /embed endpoints. Attackers can craft requests using IPv6 literal syntax to access services on the loopback interface and retrieve sensitive internal content.

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

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


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

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

## Is CVE-2026-73058 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73058 is a medium-severity server-side request forgery vulnerability in stoatchat, published on 16 Aug 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-73058 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-73058/ (Markdown: https://insights.sbomify.com/CVE-2026-73058/index.md)
```

## Sources

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

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