Live › vulnerability › CVE-2026-115411
Go to dashboardcrawlseo before 0.2.4 fails to block reserved IP ranges and does not pin the validated address for outbound requests, so DNS rebinding can bypass the check. An authenticated user can make the crawler fetch internal services or cloud metadata endpoints and read titles, headings, status codes and links back through the crawl results API.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that run crawlseo on user-supplied domains are exposed, particularly self-hosted SEO or site-audit tools running inside a cloud VPC where metadata endpoints are reachable. Deployments that only crawl fixed, trusted domains or run crawlseo with no network path to internal services can skip it.
No product ranges from the sources yet.
npm ls crawlseo or the package's lockfile entrygrep -ri crawlseo in your application code0.2.4 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-115411")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.