Omnivore Server-Side Request Forgery via the scanFeeds GraphQL Query (CVE-2026-77066) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-77066

Omnivore Server-Side Request Forgery via the scanFeeds GraphQL Query

Answer in brief

CVE-2026-77066 records a Unknown severity vulnerability in Omnivore Server-Side Request Forgery via the scanFeeds GraphQL Query. The current sources do not mark it as known exploited. The current feed maps omnivore-app/omnivore (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 20, 2026Updated Aug 20, 2026Source checked Aug 20, 2026First seen by HOL Aug 20, 2026Material review Aug 20, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps omnivore-app/omnivore (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
omnivore-app/omnivoregeneric	>=0 <c4d7d8562e6b9aabb1d8e4dabca268e314baa43a	c4d7d8562e6b9aabb1d8e4dabca268e314baa43a

Recommended response

Check inventory. Check lockfiles and deployed manifests for omnivore-app/omnivore.
Review the reported fix. Update omnivore-app/omnivore to c4d7d8562e6b9aabb1d8e4dabca268e314baa43a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 20, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.