{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77067 exists.","fix":"No fix has been published for CVE-2026-77067 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77067 is a medium-severity server-side request forgery vulnerability in omnivore-app omnivore, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77067 and fix it if it is affected.\n\nWhat it is: CVE-2026-77067 is a medium-severity server-side request forgery vulnerability in omnivore-app omnivore, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77067 exists.\n\nAffected product: omnivore-app omnivore. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77067/ (Markdown: https://insights.sbomify.com/CVE-2026-77067/index.md)","id":"CVE-2026-77067","markdown":"https://insights.sbomify.com/CVE-2026-77067/index.md","name":"CVE-2026-77067","record":{"aliases":["GHSA-w562-g8x6-3cj6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Omnivore web application","requires_auth":"low_privilege","summary":"Authenticated users can trigger server-side requests to internal endpoints via webhook URLs, potentially accessing sensitive internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Omnivore Stored Server-Side Request Forgery via the setWebhook Mutation","id":"CVE-2026-77067","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"n8n before 2.34.1 Remote Code Execution via Path Traversal","id":"CVE-2026-77068"},"packages":[],"prev":{"headline":"Omnivore Server-Side Request Forgery via the scanFeeds GraphQL Query","id":"CVE-2026-77066"},"products":["omnivore"],"published":"2026-08-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["omnivore-app"]},"summary":"Authenticated users can trigger server-side requests to internal endpoints via webhook URLs, potentially accessing sensitive internal resources.","url":"https://insights.sbomify.com/CVE-2026-77067/"}