/

CVE-2026-19762

Severity:

HIGH RISK

(7.3)

Path Traversal (CWE-22) in Taier Chunk-Check Endpoint

CVE-2026-19762

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Unauthorized File Access

Severity:

HIGH RISK

(7.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 path traversal vulnerability in DTStack Taier 1.4.0 allows remote requests to influence file-path handling in the Chunk-Check endpoint.

If the endpoint accepts attacker-controlled names without sufficiently restricting their resolved location, an attacker may access files outside the intended directory.

Affected context

The issue occurs in the Chunk-Check component, specifically in the Paths.ge function within FileChunkController.java. It becomes risky when the endpoint uses the Name argument to construct or resolve filesystem paths without reliably constraining the result to an approved base directory.

Exploit preconditions

  • Attack surface: Remotely accessible Chunk-Check endpoint
  • Required access: The ability to send requests to the affected endpoint; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the Name argument by the path-resolution logic
  • Why exploitation is possible: Insufficient canonicalization and boundary validation may allow a supplied path to resolve outside the intended directory

Why this happens

The underlying bug is improper limitation of a pathname to an intended directory. When user-controlled path components are combined with an application-controlled base path without canonicalization and containment checks, traversal sequences or equivalent path forms may reference unintended filesystem locations.

This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').

Potential impact

  • An attacker may read sensitive files accessible to the Taier process
  • The application may disclose credentials, configuration data, or operational metadata
  • Exposed files could support follow-on compromise of connected services
  • An attacker could potentially alter files if the endpoint or process grants write access

General mitigation guidance

Mitigation generally focuses on reducing trust in path input and enforcing filesystem boundaries.

Common defensive patterns include:

  • Resolve requested paths against a fixed, trusted base directory
  • Canonicalize paths before authorization checks
  • Verify that the resolved path remains within the approved directory
  • Prefer opaque identifiers or server-managed file mappings over client-supplied filenames
  • Reject absolute paths, traversal segments, and unexpected path formats
  • Apply least-privilege filesystem permissions to the service account
  • Avoid exposing sensitive directories to application-controlled file operations
  • Use read-only access where file modification is not required

How teams detect issues like this

Organizations can identify path traversal risks through:

  • Static analysis rules for filesystem APIs that consume request parameters
  • Code review checks for missing canonicalization and containment validation
  • Tests covering encoded, absolute, normalized, and alternate path representations
  • Web application policies that restrict file names to approved identifiers or patterns
  • Runtime monitoring for requests containing traversal indicators or unexpected filesystem targets
  • Automated security review tools that flag user-controlled data reaching path-resolution and file-access functions

Sources

SourceLink
github.comgithub.com/DTStack/Taier/
github.comgithub.com/DTStack/Taier/issues/1203
vuldb.comvuldb.com/cve/CVE-2026-19762
vuldb.comvuldb.com/submit/868966
vuldb.comvuldb.com/vuln/389665
vuldb.comvuldb.com/vuln/389665/cti

Frequently asked

questions

Yes. The described attack surface is a remotely accessible Chunk-Check endpoint. Successful exploitation still depends on the endpoint being reachable and on deployment-specific access controls.

An attacker needs the ability to submit requests containing a controlled Name argument. Whether authentication is required depends on how the endpoint is exposed and protected.

Resolve paths against a trusted base directory, canonicalize the result, and verify that it remains within the permitted directory before performing file operations.

Prefer server-side file identifiers, validate path inputs centrally, apply least-privilege filesystem permissions, and include traversal-focused tests and static analysis in development pipelines.

Find out what's already
exploitable in your codebase.