VulnerabilityPublished 28 Oct 2026

CVE-2026-118586: dfm feedfinder2 · Server-Side Request Forgery

Affects dfm feedfinder2Source CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 28 Oct 2026, 23:57 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
dfmfeedfinder2	Affected 0.0.1 – 0.0.4 4 affected builds	Fixed in–
PyPIfeedfinder2`pkg:pypi/feedfinder2`Other threats	Affected 0.0.1 – 0.0.4 4 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:dfm:feedfinder2:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor the project for updates and consider implementing network-level restrictions to limit the server's ability to make arbitrary outbound requests as a temporary mitigation.

Description

CVE-2026-118586 is a server-side request forgery (SSRF) vulnerability in the dfm feedfinder2 project affecting versions 0.0.1 through 0.0.4. The flaw exists in the find_feeds function of feedfinder2.py, allowing remote attackers to manipulate requests and potentially cause the server to make unintended requests. The vulnerability has a medium severity rating with a CVSS score of 6.9. No patch or vendor response has been reported yet.

Impact

An attacker can remotely exploit this SSRF vulnerability to make the server send arbitrary requests, which may lead to information disclosure or interaction with internal network resources. The impact is rated medium, reflecting the potential for misuse but no confirmed exploitation or further privilege escalation reported.

Summary

This vulnerability in dfm feedfinder2 up to version 0.0.4 involves the find_feeds function in feedfinder2.py, which can be manipulated to perform server-side request forgery (SSRF). SSRF allows an attacker to induce the server to send crafted requests to internal or external systems, potentially bypassing network restrictions. The issue was reported early to the project but remains unaddressed. Remote exploitation is possible without authentication or user interaction, as indicated by the CVSS vector.

References

Community reviews

Loading reviews…