CWE-863: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Consequences

• Confidentiality: Read Application Data, Read Files or Directories
• Integrity: Modify Application Data, Modify Files or Directories
• Access Control: Gain Privileges or Assume Identity, Bypass Protection Mechanism
• Confidentiality, Integrity, Availability: Execute Unauthorized Code or Commands
• Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)

How to prevent it

• Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
• Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
• Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
• Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
• System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

Recent advisories

• GHSA-9v7c-q64q-vv33 — Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
• EEF-CVE-2026-115627 — AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows
• EEF-CVE-2026-115635 — AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set
• EEF-CVE-2026-114214 — Loading a through relationship with a limit of 1 in Ash ignores the through path and returns unrelated destination records
• GHSA-xp3q-r38w-vgqm — SiYuan: The publish filter for local storage returns the administrator's entire storage map with only three keys sanitized
• GHSA-2phh-27fw-q4gc — PhpSpreadsheet: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading
• GHSA-vjh5-4x84-xrqp — Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive
• GHSA-6gq8-jgmh-3ffp — Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes
• GHSA-xf6w-q65w-4f2w — ApostropheCMS: The general public can access @apostrophecms/user objects via a relationship (viewRole is not applied to the general public)
• GHSA-2j32-q6rx-h844 — ApostropheCMS: Page REST API authorization bypass
• CVE-2026-110867 — Renovate before 44.60.1 contains an allowlist bypass vulnerability that allows repositories to set restricted environment variables by placing env inside a…
• GHSA-fmxq-cgp8-87wp — Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
• GHSA-fmmf-xq98-g327 — Vikunja: Write-level project members can delete admin-tier link shares through an unloaded permission check
• GHSA-hjx8-qv73-f7cm — Vikunja: Webhooks and link shares survive every revocation path, so a removed collaborator keeps a live feed
• GHSA-fprf-r6rv-xg99 — Vikunja: Saved filter creation with an empty filter string recalculates task positions across all tenants

All advisories for CWE-863