CVE-2026-77066: omnivore · Server-Side Request Forgery (SSRF)
Affects omnivoreSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to c4d7d8562e6b9aabb1d8e4dabca268e314baa43a when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c4d7d8562e6b9aabb1d8e4dabca268e314baa43a
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
Upgrade omnivore to c4d7d8562e6b9aabb1d8e4dabca268e314baa43a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| omnivore-appomnivore | Affected
| Fixed in
|
GitHubomnivorepkg:github/omnivoreOther 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
If you cannot patch yet, users should consider restricting authenticated user input to trusted URLs or implementing server-side validation similar to validateUrl() to reject private and reserved IP ranges in the scanFeedsResolver function.
Description
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.
References
- github.com/omnivore-app/omnivore/issues/4647 (opens in a new tab)
- github.com/omnivore-app/omnivore/commit/c4d7d8562e6b9aabb1d8e4dabca268e314baa43a (opens in a new tab)
- github.com/omnivore-app/omnivore/blob/0d66408746788e07cec43928581b2567308ab575/packages/api/src/resolvers/subscriptions/index.ts (opens in a new tab)
- github.com/omnivore-app/omnivore (opens in a new tab)
- vulncheck.com/advisories/omnivore-server-side-request-forgery-via-the-scanfeeds-graphql-query (opens in a new tab)