CVE-2026-68558

Received Received - Intake

SSRF Vulnerability in Wekan Kanban

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: GitHub, Inc.

Description

Wekan is open source kanban built with Meteor. From 8.36 until 9.74, the outgoing webhook Integration URL validator in models/integrations.js checked only the literal URL.hostname against regular expressions, so DNS names such as 169-254-169-254.nip.io passed that first-line check. The delivery path's fetchSafe guard already blocked the reported IPv4 destination, but its separate IPv4-only resolver and duplicated blocklist created inconsistent all-address-family enforcement and drift risk between input-time and connection-time validation. Version 9.74 makes server/lib/ssrfGuard.js resolve all addresses with `dns.lookup({ all: true })`, validate every result through the shared isIpBlocked logic, pin the connection, and block redirects. This issue is fixed in version 9.74.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-19

Last Modified

2026-08-19

Generated

2026-08-20

AI Q&A

2026-08-20

EPSS Evaluated

N/A

NVD

CVE-2026-68558

EUVD

EUVD-2026-62701

Affected Vendors & Products

Vendor	Product	Version / Range
wekan	wekan	to 9.74 (inc)
wekan	wekan	From 8.36 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

CVE-2026-68558 is a Server-Side Request Forgery (SSRF) vulnerability in Wekan, an open-source kanban tool. It allows attackers with board admin privileges to bypass IP blocklists by using public hostnames that resolve to internal or blocked IP addresses (e.g., 169-254-169-254.nip.io resolving to 169.254.169.254). The issue stems from an incomplete fix in the outgoing webhook URL validator, which checked hostnames without resolving DNS, enabling SSRF attacks.

Detection Guidance

To detect this vulnerability, check if your Wekan instance is running a vulnerable version (v8.36 to v9.73). Inspect outgoing webhook configurations for URLs using public hostnames that resolve to private or loopback IPs (e.g., 169-254-169-254.nip.io). Review server logs for unexpected internal network connections initiated by Wekan.

Impact Analysis

An attacker could exploit this to send HTTP requests to internal services, probe internal networks, or access cloud metadata services like 169.254.169.254. While the attacker cannot see responses (blind SSRF), they could interact with internal endpoints, potentially leading to data exfiltration, service disruption, or further network compromise. The attack requires low privileges (board admin) and is network-based with low complexity.

Compliance Impact

This SSRF vulnerability could lead to unauthorized access to internal systems, potentially exposing sensitive data. For GDPR, this may violate Article 32 (security of processing) if personal data is compromised. For HIPAA, it could risk protected health information (PHI) if internal systems are accessed. Compliance may require patching, audits, and breach notifications depending on the impact.

Mitigation Strategies

Upgrade Wekan to version 9.74 or later immediately. Ensure all outgoing webhook URLs are validated against resolved IPs, not just hostnames. Block internal network access from Wekan servers and monitor for unusual outbound connections.

Hi! I’m here to help you understand CVE-2026-68558. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70