CVE-2026-125366
Received Received - Intake

Authenticated SSRF in Omnom via Arbitrary Feed URL Submission

Vulnerability report for CVE-2026-125366, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-10

Last updated on: 2026-11-10

Assigner: VulnCheck

Description

Omnom through 0.9.0 contains a server-side request forgery vulnerability that allows authenticated users to make server requests to arbitrary hosts by submitting feed URLs to /add_feed. Attackers can supply internal addresses that getFeedInfo, gofeed ParseURL, and fetchImageAsInlineURL fetch without validation, using reflected error messages to probe internal hosts and ports.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-10
Last Modified
2026-11-10
Generated
2026-11-10
AI Q&A
2026-11-10
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
asciimoo omnom From 0 (inc) to 0.9.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in the omnom application up to version 0.9.0. Authenticated users can submit feed URLs via the /add_feed route to make the server request arbitrary hosts. The server functions getFeedInfo, gofeed ParseURL, and fetchImageAsInlineURL do not validate these URLs, allowing attackers to probe internal hosts and ports using reflected error messages.

Detection Guidance

To detect this SSRF vulnerability in omnom through 0.9.0, monitor outbound HTTP requests from the omnom service to internal or unexpected hosts. Check logs for feed URL processing failures or repeated requests to private IPs like 169.254.169.254. Use network tools like tcpdump or Wireshark to inspect traffic from the omnom process.

Impact Analysis

An attacker with authenticated access could exploit this to scan internal networks, access sensitive internal services, or exfiltrate data by forcing the server to make requests to restricted endpoints. The vulnerability also allows repeated probing due to hourly feed updates fetching embedded images, prolonging exposure.

Compliance Impact

This SSRF vulnerability could lead to unauthorized access to internal systems, potentially exposing personal or sensitive data. This may violate GDPR's data protection principles and HIPAA's security requirements for safeguarding protected health information, depending on the data processed by the omnom service.

Mitigation Strategies

Upgrade omnom to a version beyond 0.9.0 where the fix is applied. Alternatively, apply the commit 01c4551 changes manually by restricting outbound requests to public destinations only and configuring allowed private exceptions in the outbound.allowed_private_destinations setting.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-125366. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...