Quick answers
- Is CVE-2026-125329 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125329 being exploited in the wild.
- How severe is CVE-2026-125329?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Kaneo before 2.13.0.
- Is there a fix for CVE-2026-125329?
- Yes: fixed in 2.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125329 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-125329?
- Check whether you run Kaneo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.13.0
Technical details
The GET /api/external-link/task/:taskId endpoint returned the full integration object including plaintext integration.config containing Gitea accessToken and webhookSecret to any workspace member regardless of role. The endpoint was gated only on workspace membership, allowing even viewers to read secrets. An attacker with workspace membership could obtain these credentials to perform unauthorized Gitea actions or forge webhook deliveries that pass HMAC verification.
Affected products
- Kaneo Kaneo before 2.13.0
Timeline
- 2026-11-10: disclosed
- 2026-08-05: patched