CVE-2026-77067: 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 19% 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:N/VI:L/VA:N/SC:N/SI:L/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, restrict webhook URL inputs to trusted domains or implement network-level controls to prevent server-side requests to internal or sensitive addresses.
Description
The setWebhookResolver in packages/api/src/resolvers/webhooks/index.ts stores the caller-supplied url without any address validation, and the file imports no validation helper. When a subscribed event fires, callWebhook in packages/api/src/jobs/call_webhook.ts issues axios.request with that url, the method and Content-Type recorded on the webhook, and a JSON body carrying the event data, so an authenticated user can make the server send repeated attacker-shaped requests to internal endpoints, including link-local metadata addresses. The request is blind: callWebhook discards the result and writes only a success line or the axios error to the server log, so the response is not returned through the API.
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/webhooks/index.ts (opens in a new tab)
- github.com/omnivore-app/omnivore/blob/0d66408746788e07cec43928581b2567308ab575/packages/api/src/jobs/call_webhook.ts (opens in a new tab)
- github.com/omnivore-app/omnivore (opens in a new tab)
- vulncheck.com/advisories/omnivore-stored-server-side-request-forgery-via-the-setwebhook-mutation (opens in a new tab)