CVE Catalog

CVE-2026-77067

MediumCVSS 5.0
Published: Updated: Translated: NVD NIST

Summary

The setWebhookResolver in the application (likely n8n) lacks validation of user-supplied URLs. An authenticated user can make the server send repeated requests to internal endpoints, including link-local metadata addresses. The response is not returned via the API, making the attack blind.

Risk Assessment

An attacker can use the server to scan the internal network or access metadata services (e.g., cloud), potentially leading to privilege escalation or data leakage.

Recommendation

Add URL validation (e.g., block private and link-local addresses) in the setWebhookResolver and other places where user-supplied URLs are used.

Other vulnerabilities in n8n

See all
Original NVD description (English source)

The setWebhookResolver in packages/api/src/resolvers/webhooks/index.ts stores the caller-supplied url without any address validation, and the file imports no validation helper. When a subscribed event fires, callWebhook in packages/api/src/jobs/call_webhook.ts issues axios.request with that url, the method and Content-Type recorded on the webhook, and a JSON body carrying the event data, so an authenticated user can make the server send repeated attacker-shaped requests to internal endpoints, including link-local metadata addresses. The request is blind: callWebhook discards the result and writes only a success line or the axios error to the server log, so the response is not returned through the API.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS