CVE-2026-68558High· 8.5▾ Twilight

Wekan is open source kanban built with Meteor

▾ Twilight zone — High severity, or a signal on a lesser flaw

Depth score47/ 100 · Moderate

impact 46.8 · likelihood 0.1 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Aug 19, 2026

Updated

Sep 9, 2026

CVSS

8.5

Vendor

—

Product

—

CWE

CWE-918

Depth score

47 · Moderate

EPSS

0.36% · p30

Platforms

—

Source

NVD

Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS history

Exploit-prediction probability, daily snapshots since Sep 9.

0.3% → 0.4%▲ 0.07%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

4 events · 23 days

Aug 19, 2026Published
Disclosed via NVD
Sep 9, 2026Record revised
Last analysed / modified upstream
Sep 9, 2026EPSS first tracked
0.3%
Sep 11, 2026EPSS peak
0.3% → 0.4%

CWE-918 #nvd

Full technical detail▾

Overview

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.

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#nvd

← Back to feed