CVE-2026-105284

Account management defines and authorizes the exact privileges granted to each account or role.

Mandates that access-control decisions are made and applied to each request before access occurs.

Requires a tamperproof, always-invoked reference monitor that performs authorization checks.

Enforces only the authorizations that were assigned, so correct assignment is a prerequisite.

Separation of duties constrains which privilege combinations may be assigned to any actor.

Least privilege directly requires that only the minimal necessary privileges are assigned to each actor.

Directly enforces least-privilege policy definition, management, and review that prevents incorrect privilege assignments.

A.5.1 only requires the existence of an overarching policy and topic-specific policies (including on access control); it does not itself perform or enforce any authorization check, so the CWE-285 weakness can still be exploited.

A.5.15 directly requires determining access needs, defining/enforcing topic-specific access control policy and rules (including need-to-know, privilege restrictions, segregation, formal authorization, role-based mapping, and consistency with classification), which stops most incorrect privilege assignments from being exploitable; the bounded remainder is incorrect assignments that arise from flawed implementation of those rules rather than from their absence.

A.5.18's provisioning, review, revocation and SoD rules (esp. a,b,c,f,i,j) directly stop most incorrect privilege assignments from being granted or persisting, with a bounded remainder in flawed implementation of the authorization step itself (see 5.9/5.15 dependency)