CVE-2026-92774: Wiki.js authorization bypass in GraphQL resolvers via tag omission

CVE-2026-92774 · Severity: medium · CVSS 4.3 · Published 2026-09-16

Wiki.js is an open-source wiki platform that allows organizations to create and manage internal documentation with access controls. This vulnerability allows attackers to bypass tag-based access restrictions and retrieve sensitive page metadata (titles, descriptions, paths) through GraphQL queries without proper authorization, potentially exposing confidential documentation to unauthorized users.

Technologies: Requarks Wiki.js. Vendors: Requarks.

Quick answers

Is CVE-2026-92774 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-92774 being exploited in the wild.
How severe is CVE-2026-92774?
Medium severity, with a CVSS score of 4.3, published 16 September 2026.
Which products and versions are affected?
Requarks Wiki.js through 2.5.314.
Is there a fix for CVE-2026-92774?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-92774 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-92774?
Check whether you run Requarks Wiki.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Wiki.js versions through 2.5.314 fail to enforce tag-based authorization checks in multiple GraphQL resolvers (pages.list, pages.tree, pages.tags, pages.searchTags, and pages.links). The vulnerability is a broken access control issue where the authorization logic omits page tags from validation, allowing an unauthenticated or low-privilege attacker to query GraphQL endpoints and retrieve restricted page metadata including titles, descriptions, paths, and associated tags. The attack requires network access to the GraphQL API endpoint but no specific authentication bypass; the bug is in the permission evaluation logic itself. Attackers can enumerate pages that should be restricted based on tag-based access policies and harvest sensitive information about organizational structure and documentation content.

Affected products

  • Requarks Wiki.js through 2.5.314

Timeline

  • 2026-09-16: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.