CWE-862: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

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
• 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-vp5q-ff62-jwqv — russh: Agent server never calls `Agent::confirm`, so keys added with the confirm constraint (`ssh-add -c`) sign without confirmation
• GHSA-98mx-cjp9-gchm — Electron: Extension tabs.query returns tab URLs and titles without the tabs permission
• GHSA-vwwx-px9w-crrc — ApostropheCMS: Missing Authorization on Notification PATCH/DELETE Endpoints
• GHSA-vmxh-77cw-65j7 — ApostropheCMS: Authenticated Object-Level Authorization Bypass in exist-in-locale Reveals Restricted Localized Draft Identifiers
• GHSA-gqh3-7856-rjjg — ApostropheCMS: :_id/locales REST route omits the public-API authorization gate its sibling read routes enforce (unauthenticated doc-existence + locale metadata disclosure)
• GHSA-2jrp-qc93-h2j8 — ApostropheCMS: Same-parent page reorder in @apostrophecms/page move() re-ranks a restricted parent's children without create authorization
• GHSA-5m22-7pfq-vp65 — ApostropheCMS: Import API bypasses publication roles for protected content
• GHSA-vh56-5m88-39rq — ApostropheCMS: GET /api/v1/@apostrophecms/page/:id bypasses viewRole restriction and exposes viewPermission-gated fields to lower-privileged users
• GHSA-5v7c-xpfp-p65m — Nginx UI OTP secure-session step-up is missing on sensitive mutation routes
• GHSA-2gc7-j998-5xx6 — Nginx UI: Account Takeover via Missing `RequireSecureSession` on User Management Endpoint
• GHSA-w2ch-4xgr-22ww — Vikunja: Task relation deletion does not check read access to the other task, allowing cross-project relation removal
• GHSA-3hc7-r24j-rpwc — Vikunja: Cross-project task disclosure through subtask expansion
• GHSA-g38j-7v97-x298 — Vikunja: CalDAV relation creation bypasses TaskRelation.CanCreate, allowing an unauthorized write into any task by known UID
• GHSA-q6wp-fr43-gm9v — Contao: Improper access control in the preview links module
• GHSA-h246-wpgf-vmq5 — Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up

All advisories for CWE-862