CVE-2026-68558Public exploitNetwork attack vector

Authenticated SSRF via DNS hostname validation

Published Aug 19, 2026 · Updated Aug 19, 2026

Server-side request forgery in WeKan 8.36 through 9.73 allows remote authenticated users to reach internal HTTP services via webhook URLs. The outgoing webhook validator in models/integrations.js blocks only literal URL.hostname patterns and never resolves DNS, so names such as 169-254-169-254.nip.io pass validation and resolve to blocked loopback, link-local, or private addresses when the webhook fires. Any user who can administer a board can create an outgoing integration and trigger blind POST requests to internal services or cloud metadata endpoints, but the response body is not returned to the attacker.

CVSS severity8.5
High
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Server-side request forgery in WeKan 8.36 through 9.73 allows remote authenticated users to reach internal HTTP services via webhook URLs. The outgoing webhook validator in models/integrations.js blocks only literal URL.hostname patterns and never resolves DNS, so names such as 169-254-169-254.nip.io pass validation and resolve to blocked loopback, link-local, or private addresses when the webhook fires. Any user who can administer a board can create an outgoing integration and trigger blind POST requests to internal services or cloud metadata endpoints, but the response body is not returned to the attacker.

The record

CVE
CVE-2026-68558
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
WeKan
Product
WeKan
Classifications
CWE-918, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 8.36, < 9.74

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

WeKan · WeKanversion=>= 8.36, < 9.74

Published CVSS scores

8.5GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo