# CVE-2026-125329: Kaneo: Gitea integration access token and webhook secret exposed to any workspace member


- **Severity:** High 8.4 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-43pc-xpv9-6566

## What is CVE-2026-125329?

CVE-2026-125329 is a high-severity vulnerability in usekaneo kaneo, published on 10 Nov 2026. 

### Official 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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-125329?


## How do I fix CVE-2026-125329?

No fix has been published for CVE-2026-125329 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125329 being exploited?

There is no known exploitation of CVE-2026-125329 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125329 and fix it if it is affected.

What it is: CVE-2026-125329 is a high-severity vulnerability in usekaneo kaneo, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125329 in the wild and no public exploit code.

Affected product: usekaneo kaneo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125329/ (Markdown: https://insights.sbomify.com/CVE-2026-125329/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125329
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125329
- OSV: https://osv.dev/vulnerability/CVE-2026-125329

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125329/
Summaries are generated and may contain mistakes; the official description above is the record.