# CVE-2026-130864: Coyote before commit d6e8fb9 Missing Authorization via Wiki Comment Save Endpoint


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-64p3-j4x5-3pvc

## What is CVE-2026-130864?

CVE-2026-130864 is a medium-severity vulnerability in Coyote-OSS Coyote, published on 17 Nov 2026. 

### Official description

Coyote before commit d6e8fb9 contains a missing authorization vulnerability in Wiki\CommentController::save that allows authenticated users to edit other users' wiki comments. Attackers can send POST requests to /Comment/Save/{wiki}/{id} with another user's comment id, bypassing the WikiCommentPolicy update check, so altered text appears under the original author's name.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-130864 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130864 is a medium-severity vulnerability in Coyote-OSS Coyote, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130864 in the wild and no public exploit code.

Affected product: Coyote-OSS Coyote. 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-130864/ (Markdown: https://insights.sbomify.com/CVE-2026-130864/index.md)
```

## Sources

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

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