CWE-862: Missing Authorization
Sources read 2026-10-30. MITRE's own page · All weakness notes · Added to CISA's list in the last seven days
What it is
From MITRE's CWE catalogue
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
MITRE classes it as a class-level weakness and rates the likelihood of exploit as high.
What it lets an attacker do
From MITRE's CWE catalogue
- Read Application Data, Read Files or Directories (affects: confidentiality)
- Modify Application Data, Modify Files or Directories (affects: integrity)
- Gain Privileges or Assume Identity, Bypass Protection Mechanism (affects: access control)
- DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other) (affects: availability)
On CISA's exploited list
From CISA's exploited list
2 of the 110 entries CISA added from 2026-08-02 to 2026-10-30 name CWE-862, against 1 of 69 in the 90 days before. Over the whole catalogue 13 entries name it. The counts are small, so read them as a rough order, not a rate.
CISA's list is not every flaw that is exploited: it holds the ones CISA has evidence of, listed on the day it added them.
- CVE-2026-111357, Ivanti Connect Secure, added 2026-10-30
- CVE-2026-84869, ConnectWise ScreenConnect, added 2026-09-11
- CVE-2022-0492, Linux Kernel, added 2026-06-02
- CVE-2024-57726, SimpleHelp SimpleHelp, added 2026-04-24
- CVE-2023-52163, Digiever DS-2105 Pro, added 2025-12-22
How MITRE says to find it
From MITRE's CWE catalogue
- Automated Static Analysis
- Automated Dynamic Analysis
- Manual Analysis
- Manual Static Analysis - Binary or Bytecode
- Dynamic Analysis with Automated Results Interpretation
What MITRE suggests
From MITRE's CWE catalogue
These are MITRE's suggestions, quoted as it gives them. They are not a complete fix and not a substitute for reading the vendor's advisory for the product you run.
- 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.
- 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.
- 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.
Attack patterns MITRE links to it
From MITRE's CWE catalogue
Start with one piece of work.
Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.
Talk to us