CVE-2026-26957 is a low severity vulnerability with a CVSS score of 0.0. No known exploits currently, and patches are available.
Very low probability of exploitation
EPSS predicts the probability of exploitation in the next 30 days based on real-world threat data, complementing CVSS severity scores with actual risk assessment.
Date: 2025-12-07 Vulnerability: Server-Side Request Forgery (SSRF) Component: Webhooks Module
A critical security vulnerability exists in the LibreDesk Webhooks module that allows an authenticated "Application Admin" to compromise the underlying cloud infrastructure or internal corporate network where this service is being hosted.
The application fails to validate destination URLs for webhooks. This allows an attacker to force the server to make HTTP requests to arbitrary internal destinations.
Attackers can map the internal network by observing the difference between successful connections and connection errors. This works even if the response body is not returned.
Proof of Exploitation (from Server Logs):
timestamp=... level=info message="webhook delivered successfully" ... status_code=200
timestamp=... level=error message="webhook delivery failed" ... error="... connect: connection refused"
Impact: An attacker can identify running services (databases, caches, internal apps) on the local network (e.g., localhost, 192.168.x.x).
If the internal service returns a non-2xx response (e.g., 403 Forbidden, 404 Not Found, 500 Error), the application logs the full response body.
Proof of Exploitation (from Server Logs):
timestamp=... level=error message="webhook delivery failed" ...
response="{\"secret_key\": \"xxx123\", \"role\": \"admin\"}"
Impact: An attacker can extract sensitive data by targeting endpoints that return errors or by forcing errors on internal services.
Please cite this page when referencing data from Strobes VI. Proper attribution helps support our vulnerability intelligence research.
cmd/webhooks.go only checks if the URL is empty, not if it resolves to a private IP.internal/webhook/webhook.go uses a default http.Client that follows redirects and connects to any IP.To prevent this, the application must implement Defense in Depth:
http.Transport that verifies the destination IP address after DNS resolution to prevent DNS rebinding attacks.