CVE-2026-118586
dfm feedfinder2 feedfinder2.py find_feeds server-side request forgery
A security flaw has been discovered in dfm feedfinder2 up to 0.0.4. This issue affects the function find_feeds of the file feedfinder2.py. Performing a manipulation results in server-side request forgery. Remote exploitation of the attack is possible. The project was informed of the problem early through an issue report but has not responded yet.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| feedfinder2 dfm |
0.0.1 (affected) 0.0.2 (affected) 0.0.3 (affected) 0.0.4 (affected) |
CNA: VulDB |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 6.9 medium |
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 | CNA: VulDB |
| 3.1 / 5.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:C | CNA: VulDB |
| 3.0 / 5.3 medium |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:C | CNA: VulDB |
| 2.0 / 5.0 medium |
AV:N/AC:L/Au:N/C:P/I:N/A:N/E:ND/RL:ND/RC:C | CNA: VulDB |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://vuldb.com/vuln/428026CNA: VulDB · vdb-entry, technical-description
- https://vuldb.com/vuln/428026/ctiCNA: VulDB · signature, permissions-required
- https://vuldb.com/cve/CVE-2026-118586CNA: VulDB · third-party-advisory
- https://vuldb.com/submit/1026092CNA: VulDB · third-party-advisory
- https://github.com/dfm/feedfinder2/issues/16CNA: VulDB · issue-tracking
- https://github.com/dfm/feedfinder2/CNA: VulDB · product
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.