Skip to content
OpenAdvisories

Weakness (CWE)

CWE-1220: Insufficient Granularity of Access Control

Base Incomplete

The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack the required granularity

How to prevent it (1 mitigation)
  1. Architecture and Design, Implementation, Testing

    - Access-control-policy protections must be reviewed for design inconsistency and common weaknesses.

    - Access-control-policy definition and programming flow must be tested in pre-silicon, post-silicon testing.

Source: MITRE CWE-1220

4 results · Clear filters · Feed

  • High 7.4
    CVE-2026-78122 Public exploit

    docker-socket-proxy through 0.5.0 Insufficient Access Control Granularity Exposes Container Filesystems

    docker-socket-proxy fails to properly gate read endpoints in the /containers Docker API namespace when the CONTAINERS environment variable is set. Attackers can use GET requests to /containers/{id}/archive, /containers/{id}/export, /containers/{id}/logs, and …

  • High 7.8
    CVE-2026-33825 Exploited · Ransomware Public exploit

    Microsoft Defender Elevation of Privilege Vulnerability

    Insufficient granularity of access control in Microsoft Defender allows an authorized attacker to elevate privileges locally.

    KEV Apr 22, 2026
  • High 8.2
    CVE-2026-39363 Public exploit

    Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket

    Vite is a frontend tooling framework for JavaScript. From 6.0.0 to before 6.4.2, 7.3.2, and 8.0.5, if it is possible to connect to the Vite dev server’s WebSocket without an Origin header, an attacker can invoke fetchModule via the custom WebSocket event vite…

  • High 7.4
    CVE-2024-42365 Public exploit

    Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan

    Asterisk is an open source private branch exchange (PBX) and telephony toolkit. Prior to asterisk versions 18.24.2, 20.9.2, and 21.4.2 and certified-asterisk versions 18.9-cert11 and 20.7-cert2, an AMI user with `write=originate` may change all configuration …