CVE
Fider: Server-Side Request Forgery (SSRF) via Webhook URL
Fider versions before 0.34.0 are affected when webhook URLs take user-supplied values that the server fetches. The fix is in 0.34.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.34.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Fider versions before 0.34.0 are affected Webhook URLs are configured with user-supplied values that the server fetches
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Fider, a feedback portal, has a server-side request forgery flaw in its webhook URL handling that lets a logged-in user with administrative privileges make the server send arbitrary HTTP requests remotely over the network. Through this, an attacker could reach internal services or cloud metadata endpoints.
Read the original description
Fider is a feedback portal for feature requests and suggestions. Prior to version 0.34.0, a Server-Side Request Forgery (SSRF) vulnerability exists in Fider due to insufficient validation of webhook URLs. The application allows user-controlled URLs to be fetched by the server without restricting access to internal or external network resources. This enables attackers with administrative privileges to make arbitrary HTTP requests from the server, potentially accessing internal services or cloud metadata endpoints. This issue has been patched in version 0.34.0.
Who should check
Teams running self-hosted Fider before 0.34.0 with webhooks configured, where admins can set webhook URLs
Read the source excerpt
“A Server-Side Request Forgery (SSRF) vulnerability exists in Fider due to insufficient validation of webhook URLs.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Fider versions before 0.34.0 are affected Webhook URLs are configured with user-supplied values that the server fetchesUpgrade to a fixed version: 0.34.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-65967 (Fider: Server-Side Request Forgery (SSRF) via Webhook URL), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-65967 (entry last updated 2026-11-11):
Affected:
- getfider fider: fixed in 0.34.0
Fixed versions: 0.34.0.
Conditions (all must be true for the bug to be hit):
- Fider versions before 0.34.0 are affected (source: https://github.com/getfider/fider/security/advisories/GHSA-g445-xwm7-594r)
- Webhook URLs are configured with user-supplied values that the server fetches (source: https://github.com/getfider/fider/security/advisories/GHSA-g445-xwm7-594r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-65967 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-65967 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getfider/fider/security/advisories/GHSA-g445-xwm7-594r
- https://github.com/getfider/fider/releases/tag/v0.34.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-65967
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-65967"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- getfider fider
fixed in 0.34.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-65967
Is CVE-2026-65967 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Fider accepts webhook URLs from user input and the server fetches them, so a request can be made from the Fider server to internal services, localhost, private networks and cloud metadata endpoints, potentially exposing credentials or data.Source: github.com
Which versions are affected by CVE-2026-65967?
fider: before 0.34.0.Source: cve.now feed data
Am I affected, and how do I check?
Fider versions before 0.34.0 are affected, in setups where webhook URLs are configured with user-supplied values that the server fetches. To check, look up the installed Fider version and whether webhooks are configured.Source: github.com
How do I fix CVE-2026-65967?
Upgrade Fider to 0.34.0 or later, which includes the patch (commit f7db8603).Source: github.com