Skip to main content
VulnerabilityPublished

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

Affects feedfinder2Source GCVE Database

0
Authoritative record:CVE-2026-118586· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 29 Oct 2026, 01:14 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Affects
dfm feedfinder2 up to 0.0.4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubdfm/feedfinder2pkg:github/dfm/feedfinder2Other threatsAffected
  • <=0.0.4
Fixed in–

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 protections to restrict outgoing requests from the affected service until a patch is released.

Description

A security flaw in dfm feedfinder2 up to version 0.0.4 allows remote attackers to perform server-side request forgery (SSRF) via the find_feeds function in feedfinder2.py. This vulnerability enables an attacker to manipulate server requests, potentially accessing internal resources. The issue was reported to the project early, but no response or fix has been issued yet.

References

Community reviews

Loading reviews…