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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.13.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Task has a linked Gitea issue or pull request A Gitea integration is configured in Kaneo Kaneo version before 2.13.0
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Read the original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Task has a linked Gitea issue or pull request A Gitea integration is configured in Kaneo Kaneo version before 2.13.0Upgrade to a fixed version: 2.13.0.
Workaround: Remove Gitea integrations, which clears the exposed configuration.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- usekaneo kaneo
fixed in 2.13.0
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125329
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-125329?
kaneo: before 2.13.0.Source: cve.now feed data
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: github.com
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: github.com