# CVE-2026-92774: Wiki.js through 2.5.314 Authorization Bypass via GraphQL Tag Omission

> Attackers can bypass tag-based access restrictions in Wiki.js GraphQL resolvers to read restricted page metadata without authorization.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-69p6-97m5-6vpp

## What is CVE-2026-92774?

CVE-2026-92774 is a medium-severity missing authorization vulnerability in requarks Wiki.js, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wiki.js through 2.5.314 omits page tags from authorization checks in multiple GraphQL resolvers, allowing tag-based access restrictions to be bypassed. Attackers can query the list, tree, tags, searchTags, and links resolvers to retrieve restricted page metadata including titles, descriptions, paths, and tag information without proper authorization.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92774 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92774 is a medium-severity missing authorization vulnerability in requarks Wiki.js, published on 16 Sep 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-92774 exists.

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

## Sources

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

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