/

CVE-2026-36851

Severity:

HIGH RISK

(7.5)

Path Traversal (CWE-22) in UnPoller Password Field

CVE-2026-36851

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Arbitrary File Read and Network Exfiltration

Severity:

HIGH RISK

(7.5)

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 UnPoller 2.33.0 allows specially crafted input in the password field to access files outside the intended location. Depending on deployment permissions and network connectivity, an attacker may read sensitive data and cause it to be sent to an external destination.

Affected context

The issue occurs in UnPoller deployments where the password field is processed as a file-related value without sufficiently restricting its path semantics. Risk is higher when the service has access to sensitive local files or can make outbound network connections, and when untrusted users or systems can influence authentication or configuration input.

Exploit preconditions

  • Attack surface: UnPoller's password-handling functionality
  • Required access: Ability to submit or modify a value processed by the password field
  • Trigger point: Processing of the crafted password value by the application
  • Why exploitation is possible: Input is interpreted as a filesystem path without adequately constraining traversal outside the intended directory
  • Environmental factors: File permissions and outbound network access affect the scope of readable data and possible exfiltration

Why this happens

The underlying flaw is improper neutralization of path elements in user-controlled input. When a value intended to represent a password is treated as a filesystem path without canonicalization, allowlisting, or confinement to an approved directory, traversal sequences may resolve to unintended files. This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.

Potential impact

  • An attacker may read sensitive local files
  • Credentials, tokens, or configuration data could be exposed
  • Read information could be transmitted to an attacker-controlled network destination
  • The service's confidentiality could be reduced
  • Exposed secrets could enable follow-on access to connected systems

General mitigation guidance

Mitigation generally focuses on ensuring password-related inputs are treated as data rather than unrestricted filesystem paths.

Common defensive patterns include:

  • Using fixed, secure mechanisms for secret retrieval instead of user-controlled paths
  • Applying strict allowlists for any file-based secret references
  • Canonicalizing paths and enforcing confinement within an approved directory
  • Rejecting traversal components, unexpected separators, and ambiguous path forms
  • Running the service with least-privilege filesystem permissions
  • Restricting unnecessary outbound network connectivity
  • Avoiding sensitive data in broadly readable files

How teams detect issues like this

Detection approaches may include:

  • Static analysis for filesystem APIs that consume authentication or configuration fields
  • Code review checks for missing canonicalization, path confinement, or allowlisting
  • Tests using traversal variants and platform-specific path representations
  • Runtime monitoring for unusual reads outside approved directories
  • Egress monitoring for unexpected transfers following file-access events
  • Policy enforcement requiring least-privilege service accounts and restricted network destinations

Automated security review tools may help identify path construction and validation weaknesses.

Sources

SourceLink
github.comgithub.com/SyntaxSaiyan/CVE-2026-36851
github.comgithub.com/unpoller/unpoller

Frequently asked

questions

It may be exploitable through a remotely reachable UnPoller interface if an attacker can influence the password field. Exploitability depends on exposure, authentication controls, and deployment configuration.

The key requirement is the ability to provide or modify a value that reaches the vulnerable password-processing path. The impact also depends on the service account's file permissions and network access.

Treat password values as opaque secrets, avoid interpreting them as unrestricted paths, and enforce canonicalized path allowlisting when file references are necessary.

Combine strict input validation with filesystem confinement, least-privilege permissions, secret-management controls, and monitoring for unexpected file access or outbound transfers.

Find out what's already
exploitable in your codebase.