Vulnerability in Kaneo (CVE-2026-63104)
Summary
Vulnerability in Kaneo (CVE-2026-63104). Data can be tampered with by attackers. Exploitable via PATCH /api/task/bulk.
Original description
The description as published by the source.
Kaneo versions 2.3.12 before 2.12.2 contain a missing authorization vulnerability that allows authenticated workspace members with viewer or member roles to delete and modify tasks beyond their assigned permissions by exploiting the bulk task endpoint that omits workspace permission checks. Attackers can send requests to the PATCH /api/task/bulk endpoint, which verifies only workspace membership without calling the role-based permission check enforced on all other task endpoints, to permanently delete all tasks or modify task status, priority, assignee, due date, and labels in a workspace.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63104 has been found in Kaneo.
Attackers can target a specific entry point like PATCH /api/task/bulk over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Kaneo CVE-2026-63104" on the vendor's site.
CVE-2026-63104 (Kaneo) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/task/bulk
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Kaneo. Attackers reach the vulnerable code path via PATCH /api/task/bulk.
Check the vendor advisory for the affected versions of Kaneo. Attack surface: PATCH /api/task/bulk.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /api/task/bulk requests with malformed payloads or SQL meta-characters. Run grep -r 'Kaneo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Kaneo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Kaneoを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PATCH /api/task/bulk' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/task/bulkへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PATCH /api/task/bulk on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。