CVE-2026-115411: crawlseo · Server-Side Request Forgery (SSRF)
Affects crawlseoSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.2.4 when convenient.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.2.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade crawlseo to 0.2.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| crawlseocrawlseo | Affected
| Fixed in
|
GitHubcrawlseopkg:github/crawlseoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in crawlseo version 0.2.4. Users should upgrade to version 0.2.4 or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
crawlseo versions before 0.2.4 have a server-side request forgery (SSRF) vulnerability in the crawler engine. The isPrivateIp() function fails to block certain reserved IP ranges and does not pin the validated address for outbound connections, allowing a time-of-check to time-of-use (TOCTOU) DNS rebinding bypass. An authenticated attacker can add a malicious domain resolving to internal or restricted addresses, trigger a crawl, and access internal services or cloud metadata endpoints such as 169.254.169.254. The attacker can then retrieve information like page titles, descriptions, headings, status codes, and links via the crawl results API, enabling internal network reconnaissance.
References
- github.com/crawlseo/crawlseo/commit/76e4e693de0c6b294cf1f60656800e47346f1c28 (opens in a new tab)
- github.com/crawlseo/crawlseo/releases?page=1 (opens in a new tab)
- gist.github.com/mansurmavlankulov/47cb8e183fec39a7afe599d1082a3399 (opens in a new tab)
- vulncheck.com/advisories/crawlseo-before-server-side-request-forgery-via-crawler (opens in a new tab)