CWE-732: Incorrect Permission Assignment for Critical Resource
Sources read 2026-11-13. 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 specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
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)
- Gain Privileges or Assume Identity (affects: access control)
- Modify Application Data, Other (affects: integrity, other)
On CISA's exploited list
From CISA's exploited list
1 of the 110 entries CISA added from 2026-08-20 to 2026-11-17 name CWE-732, against 0 of 70 in the 90 days before. Over the whole catalogue 3 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-123039, Check Point Multiple Products, added 2026-11-13
- CVE-2018-13374, Fortinet FortiOS and FortiADC, added 2022-09-08
- CVE-2019-15752, Docker Desktop Community Edition, added 2021-11-03
How MITRE says to find it
From MITRE's CWE catalogue
- Automated Static Analysis
- Automated Dynamic Analysis
- Manual Analysis
- Manual Static Analysis
- Manual Dynamic Analysis
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.
- Implementation: When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user) [REF-62], and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Architecture and Design: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
- Architecture and Design: Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- Implementation: During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
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