CVE-2026-77066: Omnivore Server-Side Request Forgery via the scanFeeds GraphQL Query
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-08-20).
Weakness: Server-Side Request Forgery (SSRF)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-63255, GHSA-w9wc-vx4j-8xwg
VEDAS cluster: VEDAS:DEEPDARKMATTER
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-77066.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-77066.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-77066.rules
Vulnerability databases and vendor advisories (3)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-63255
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-w9wc-vx4j-8xwg
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-77066
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| omnivore-app omnivore | before c4d7d8562e6b (git commit) | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-77066 Omnivore - Server-Side Request Forgery via scanFeeds resolver. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-77066 Omnivore - Server-Side Request Forgery via scanFeeds resolver"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/graphql"; nocase; fast_pattern; http.request_body; content:"scanFeeds"; nocase; pcre:"/https?(?:\x3a|%3a)(?:\x2f\x2f|%2f%2f)(?:127\.|0\.0\.0\.0|localhost|169\.254\.169\.254|metadata|10\.|192\.168\.|172\.(?:1[6-9]|2[0-9]|3[01])\.|\x5b|%5b)/i"; classtype:web-application-attack; reference:cve,CVE-2026-77066; reference:url,https://www.exploit.observer/?keyword=CVE-2026-77066&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=omnivore&match=exact; sid:1095404; rev:1;)
CVE-2026-77066.rules on GitHub
References
Vendor advisories and patches
Exploits and technical analysis
- GitHub Issue #4647 (issue-tracking)
- Unvalidated axios.get in scanFeedsResolver before the fix (technical-description)
- VulnCheck Advisory: Omnivore Server-Side Request Forgery via the scanFeeds GraphQL Query (third-party-advisory)
Other references
- https://github.com/omnivore-app/omnivore (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.