/

CVE-2026-66887

Severity:

CRITICAL RISK

(9.6)

Missing Authorization (CWE-862) in Affected Product CGIs

CVE-2026-66887

Awaiting Analysis

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized State Changes

Severity:

CRITICAL RISK

(9.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authorization vulnerability affects state-changing CGI endpoints in the affected products. When authorization checks are absent, an attacker who can reach these endpoints may perform administrative or other protected actions without the required permission.

Affected context

The issue may occur in products that expose state-changing operations through CGI endpoints but do not consistently verify the requesting user's authorization or session state. Risk is higher when these endpoints are network-reachable and can modify configuration, accounts, services, or other security-sensitive settings.

Exploit preconditions

  • Attack surface: State-changing CGI endpoints exposed by an affected product
  • Required access: Network reachability to the relevant endpoint; authentication may not be required when checks are absent
  • Trigger point: A request to a CGI that performs a protected state-changing operation
  • Why exploitation is possible: The endpoint does not adequately enforce authorization and may also omit session validation before processing the request

Why this happens

The underlying flaw is an authorization enforcement failure. State-changing CGI handlers process requests without reliably checking whether the caller has a valid session and sufficient permission for the requested operation.

This maps to CWE-862: Missing Authorization, in which an application fails to enforce access controls for a protected resource or action. The insecure pattern is treating endpoint reachability as sufficient permission rather than separately validating identity, session state, and authorization.

Potential impact

  • An attacker may change protected application or device state
  • An attacker could modify configuration or security settings
  • Unauthorized users may create, alter, or remove accounts or services
  • The affected product may experience data loss, disruption, or administrative takeover
  • Compromised settings could enable further access to connected systems

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently at every state-changing endpoint.

Common defensive patterns include:

  • Requiring authenticated, valid sessions for protected CGI operations
  • Applying server-side authorization checks for every requested action
  • Denying access by default and granting only the minimum required privileges
  • Separating read-only and state-changing interfaces with distinct access policies
  • Using centralized authorization middleware instead of relying on individual handlers
  • Reducing trust in client-supplied roles, identifiers, and action parameters
  • Protecting administrative interfaces through network segmentation and other access controls

How teams detect issues like this

Organizations can identify missing authorization through:

  • Static analysis searches for state-changing handlers lacking authentication or permission checks
  • Code review of CGI routes, especially those handling configuration, account, or service changes
  • Dynamic testing that compares authorized, unauthenticated, and lower-privileged requests
  • Endpoint inventories that classify every operation by required privilege
  • Policy enforcement requiring explicit authorization annotations or middleware for mutating routes
  • Application and web-server logs showing state-changing requests without a valid session or expected privilege

Sources

SourceLink
digital-watchdog.comdigital-watchdog.com/downloads/
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-258-01.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-258-01

Frequently asked

questions

It may be remotely exploitable when the affected CGI endpoints are reachable over a network. Exploitability depends on deployment exposure and whether additional controls restrict access.

Not necessarily. If both session validation and authorization checks are absent, network access to a relevant endpoint may be sufficient; otherwise, a low-privileged account or valid session could be required.

Require a valid session and enforce server-side, endpoint-specific authorization before performing any state-changing operation. Deny requests by default when identity or permission cannot be established.

Maintain an inventory of protected operations, apply centralized access-control middleware, test requests across privilege levels, and enforce review policies for all new state-changing endpoints.

Find out what's already
exploitable in your codebase.