# CVE-2026-115411: crawlseo before 0.2.4 Server-Side Request Forgery via Crawler


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-rvhf-6hhm-xg6w

## What is CVE-2026-115411?

CVE-2026-115411 is a medium-severity vulnerability in crawlseo, published on 22 Oct 2026. 

### Official description

crawlseo before version 0.2.4 contains a server-side request forgery vulnerability in its crawler engine where isPrivateIp() fails to block reserved IP ranges such as RFC 6598 Carrier-Grade NAT, RFC 6890, TEST-NET ranges and certain IPv6 addresses, and additionally fails to pin the validated address for the actual outbound connection, allowing a TOCTOU DNS rebinding bypass. An authenticated attacker can add a malicious domain that resolves to an internal or restricted address, trigger a crawl to reach internal services or cloud metadata endpoints like 169.254.169.254, and retrieve the fetched page's title, description, headings, status code and links through the crawl results API, enabling internal network reconnaissance.

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

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


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

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

## Is CVE-2026-115411 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115411 is a medium-severity vulnerability in crawlseo, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115411 in the wild and no public exploit code.

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

## Sources

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

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