# CVE-2026-41455: WeKan < 8.35 SSRF via Webhook URL

> Attackers can exploit SSRF in WeKan webhooks to access internal networks and modify comment data without authorization.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-qvhh-2f8h-hqgp

## What is CVE-2026-41455?

CVE-2026-41455 is a medium-severity server-side request forgery vulnerability in wekan, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WeKan before 8.35 contains a server-side request forgery vulnerability in webhook integration URL handling where the URL scheme field accepts any string without protocol restriction or destination validation. Attackers who can create or modify integrations can set webhook URLs to internal network addresses, causing the server to issue HTTP POST requests to attacker-controlled internal targets with full board event payloads, and can additionally exploit response handling to overwrite arbitrary comment text without authorization checks.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-41455?


## How do I fix CVE-2026-41455?

No fix has been published for CVE-2026-41455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41455 being exploited?

There is no known exploitation of CVE-2026-41455 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41455 and fix it if it is affected.

What it is: CVE-2026-41455 is a medium-severity server-side request forgery vulnerability in wekan, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41455 in the wild and no public exploit code.

Affected product: wekan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41455/ (Markdown: https://insights.sbomify.com/CVE-2026-41455/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41455
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41455
- OSV: https://osv.dev/vulnerability/CVE-2026-41455

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41455/
Summaries are generated and may contain mistakes; the official description above is the record.