CVE-2026-77066
The scanFeedsResolver in …
The scanFeedsResolver in packages/api/src/resolvers/subscriptions/index.ts passes the caller-supplied url straight to axios.get(url, rssParserConfig()) with no address validation. The same file guards the subscribe path with validateUrl(), which rejects private and reserved ranges through the private-ip library, and createPageSaveRequest applies the same check, so the omission is specific to this resolver. An authenticated user can direct the server to request arbitrary internal endpoints. The response is parsed as a feed or as HTML and the resolver returns the resulting url, title, description and type fields, so disclosure is limited to feed-shaped metadata and to link elements advertising RSS or Atom feeds; requests that do not parse still distinguish reachable ports from unreachable ones through the resulting error.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/omnivore-app/omnivore
- github.com/omnivore-app/omnivore/blob/0d66408746788e07cec43928581b2567308ab575/packages/ap
- github.com/omnivore-app/omnivore/commit/c4d7d8562e6b9aabb1d8e4dabca268e314baa43a
- github.com/omnivore-app/omnivore/issues/4647
- www.vulncheck.com/advisories/omnivore-server-side-request-forgery-via-the-scanfeeds-graphq
- nvd.nist.gov/vuln/detail/CVE-2026-77066
- cve.org/CVERecord?id=CVE-2026-77066
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.