CVE-2026-118586 dfm feedfinder2 feedfinder2.py find_feeds server-side request forgery
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-118586 and fix it if it is affected.
What it is: CVE-2026-118586 is a medium-severity vulnerability in dfm feedfinder2, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-118586 in the wild and no public exploit code.
Affected product: dfm feedfinder2. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-118586/ (Markdown: https://insights.sbomify.com/CVE-2026-118586/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-118586?
CVE-2026-118586 is a medium-severity vulnerability in dfm feedfinder2, published on 28 Oct 2026.
Official description
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.
Weakness: CWE-918
Which versions are affected by CVE-2026-118586?
How do I fix CVE-2026-118586?
No fix has been published for CVE-2026-118586 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-118586 being exploited?
There is no known exploitation of CVE-2026-118586 in the wild and no public exploit code.
Sources
Also known as GHSA-pgg4-2f4g-83hg.