Wekan
Wekan: SSRF filter bypass via DNS-resolving hostname in outgoing webhooks (incomplete fix of CVE-2026-53446)
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8.36, < 9.74
Fixed in 9.74
Mitigation
Upgrade wekan to 9.74 or later.
References
- Vendor advisory github.com/wekan/wekan/security/advisories/GHS…
- Patch github.com/wekan/wekan/commit/ef845fe4a0adb82a…
- Release notes github.com/wekan/wekan/releases/tag/v9.74
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.