/

CVE-2026-19979

Severity:

HIGH RISK

(8.3)

Authorization Bypass (CWE-285) in GL.iNet WebDAV Service

CVE-2026-19979

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285, CWE-639

Impact:

Unauthorized file access or modification

Severity:

HIGH RISK

(8.3)

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 high-severity authorization vulnerability in the GL.iNet WebDAV Service affects handling of COPY and MOVE operations. A remote attacker may bypass intended access controls and perform file operations when the WebDAV endpoint is reachable and the relevant authorization checks are insufficient.

Affected context

The issue may occur in GL.iNet router models including the A1300, AX1800, AXT1800, BE-series, E-series, MT-series, X-series, and XE3000 when running affected software up to the 4.8.x release line. It is associated with the WebDAV Service and its handling of COPY and MOVE requests. Risk depends on whether WebDAV is enabled, externally reachable, and protected by effective authorization controls.

Exploit preconditions

  • Attack surface: The WebDAV Service exposed through a network-accessible router interface
  • Required access: Network connectivity to the WebDAV endpoint; the precise authentication requirement depends on deployment configuration
  • Trigger point: Processing of WebDAV COPY or MOVE operations
  • Why exploitation is possible: Authorization checks may not adequately constrain file operations to the requesting user's permitted resources

Why this happens

The underlying bug is an authorization enforcement failure in a file-management protocol operation. COPY and MOVE functionality may perform actions without consistently verifying that the requester has permission to access both the source and destination resources. This behavior maps primarily to CWE-285: Improper Authorization, with CWE-639: Authorization Bypass Through User-Controlled Key also relevant when attacker-controlled resource identifiers influence access decisions.

Potential impact

  • An attacker may access files outside the intended authorization scope
  • An attacker could modify, copy, move, or overwrite accessible router files
  • Sensitive configuration data may be exposed
  • Router functionality or stored data may be disrupted
  • Compromise of files used by other services may increase follow-on risk

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every WebDAV operation and resource relationship.

Common defensive patterns include:

  • Applying centralized authorization checks to both source and destination resources
  • Canonicalizing and validating resource identifiers before permission decisions
  • Denying access by default when ownership or scope cannot be established
  • Restricting WebDAV exposure to trusted networks or administrative interfaces
  • Disabling WebDAV when it is not required
  • Running file-management services with the minimum filesystem privileges necessary
  • Separating user-controlled storage from sensitive system and configuration paths
  • Logging and rate-limiting unusual COPY and MOVE activity

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis for authorization decisions that occur only on one side of a file operation
  • Code review checks covering source, destination, path normalization, and ownership validation
  • Tests that attempt cross-user and cross-directory COPY and MOVE operations
  • Endpoint policy checks confirming that WebDAV is disabled or network-restricted where unnecessary
  • Runtime monitoring for unexpected file operations, destination changes, and access-control failures
  • Automated security testing that compares effective permissions with the permissions required by each WebDAV method

Sources

SourceLink
github.comgithub.com/gl-inet/CVE-issues/blob/main/4.0.0/WebDAV%20Public-Share%20Destination%20Authorization%20Bypass.md
vuldb.comvuldb.com/cve/CVE-2026-19979
vuldb.comvuldb.com/submit/873915
vuldb.comvuldb.com/vuln/391161
vuldb.comvuldb.com/vuln/391161/cti

Frequently asked

questions

Yes, the vulnerability is described as remotely exploitable when the affected WebDAV Service is reachable over a network. Exposure and exploitability still depend on routing, firewall, and service configuration.

The exact requirement may vary by deployment. Network access to the WebDAV endpoint is necessary, while the issue may allow an attacker to bypass authorization that would otherwise limit file operations.

Enforce authorization independently for every COPY and MOVE request, including validation of both source and destination resources after canonicalization.

Use centralized deny-by-default authorization, test cross-resource operations, restrict unnecessary WebDAV exposure, and monitor file operations for unexpected behavior.

Find out what's already
exploitable in your codebase.