# CVE-2026-104443: YesWiki before 4.6.7 Scope Bypass via Triples Delete API

> Authenticated users can bypass scope checks in the triples delete API to remove admin memberships, causing site-wide lockouts and privilege escalation.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-9j7h-ccj2-jxv6, GHSA-gr78-chgv-6fgg

## What is CVE-2026-104443?

CVE-2026-104443 is a high-severity missing authorization vulnerability in yeswiki, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

YesWiki before 4.6.7 contains an empty-filter scope bypass in the triples delete API that allows any authenticated user to delete or forge arbitrary semantic triples regardless of ownership. Attackers can send an empty filter to the triples delete endpoint to remove the admins-group membership triple, emptying the admin group and causing a site-wide authorization lockout.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-104443 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104443 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104443 is a high-severity missing authorization vulnerability in yeswiki, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104443 exists.

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

## Sources

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

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