# CVE-2026-67346: Swarms 6.8.1 Server-Side Request Forgery via DNS Rebinding Bypass

> Attackers can exploit a DNS rebinding flaw in Swarms to access internal services and exfiltrate credentials via malicious URLs.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-v37m-33r4-9ggf

## What is CVE-2026-67346?

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

### Official description

Swarms through 6.8.1, fixed in commit 8b0fc9e, contains a server-side request forgery vulnerability in the _is_safe_url function that fails to validate hostnames through DNS resolution, allowing attackers to bypass the blocklist. Attackers can supply user-controlled image or audio URLs that resolve to private, loopback, or metadata addresses to reach internal services and exfiltrate credentials.

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

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


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

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

## Is CVE-2026-67346 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67346 is a high-severity server-side request forgery vulnerability in kyegomez swarms, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67346 in the wild and no public exploit code.

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

## Sources

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

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