Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-101082 Overview
CVE-2026-101082 is a path traversal vulnerability [CWE-22] affecting PMWeb versions 7.x, 8.x, and 2025.x. The flaw resides in the downloader.aspx file, where the FullFileName and FileName parameters accept attacker-controlled input without adequate validation. Remote attackers can manipulate these parameters to traverse outside the intended directory and retrieve files from the underlying server. A public exploit is available. The vendor was contacted before disclosure but did not respond.
Critical Impact
Unauthenticated remote attackers can read arbitrary files accessible to the PMWeb application, exposing configuration data, credentials, and sensitive project documents.
Affected Products
- PMWeb 7.x
- PMWeb 8.x
- PMWeb 2025.x
Discovery Timeline
- 2026-09-28 - CVE CVE-2026-101082 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-101082
Vulnerability Analysis
The vulnerability exists in the downloader.aspx endpoint used by PMWeb to serve file downloads. The handler consumes the FullFileName and FileName request arguments and passes them into file access logic without normalizing or restricting the resolved path. An attacker can supply directory traversal sequences such as ..\ or absolute paths to escape the intended download directory.
Because the endpoint is reachable over the network and requires no authentication or user interaction, exploitation is straightforward. Successful requests return the contents of files readable by the IIS application pool identity. That set typically includes web.config files, connection strings, application binaries, uploaded project documentation, and other sensitive artifacts. Public exploit code exists, increasing the likelihood of opportunistic scanning.
Root Cause
The root cause is missing input sanitization on user-supplied file path parameters. The downloader.aspx handler trusts FullFileName and FileName as safe file references and does not enforce canonicalization, allow-listing, or containment within a designated download root. This is a classic instance of CWE-22 Improper Limitation of a Pathname to a Restricted Directory.
Attack Vector
An unauthenticated remote attacker issues an HTTP request to the downloader.aspx endpoint and supplies a traversal payload in the FullFileName or FileName parameter. The server resolves the manipulated path and returns the requested file. No prerequisites beyond network reachability to the PMWeb web interface are required. See the VulDB entry for CVE-2026-101082 for additional technical detail.
Detection Methods for CVE-2026-101082
Indicators of Compromise
- HTTP requests to downloader.aspx containing ..\, ../, %2e%2e, or absolute paths in the FullFileName or FileName parameters.
- Web server access logs showing anomalous download activity from unauthenticated sessions or unusual source IPs.
- Unexpected reads of sensitive files such as web.config, appsettings.json, or database backup files by the IIS worker process.
Detection Strategies
- Deploy WAF or IIS request filtering rules that inspect query strings on downloader.aspx for path traversal sequences and encoded variants.
- Correlate download requests against expected file inventories to identify retrieval of files outside standard project document paths.
- Baseline typical downloader.aspx request patterns and alert on outliers in parameter length, encoding, or file extensions requested.
Monitoring Recommendations
- Enable IIS advanced logging to capture full query strings and response sizes for the PMWeb application.
- Forward web server and application logs to a centralized analytics platform for retention and correlation.
- Monitor egress volumes from PMWeb servers for signs of bulk file exfiltration.
How to Mitigate CVE-2026-101082
Immediate Actions Required
- Restrict network exposure of PMWeb interfaces to trusted management networks or place them behind a VPN.
- Deploy WAF rules that block traversal patterns in requests to downloader.aspx, including URL-encoded and double-encoded variants.
- Audit IIS and web server logs for prior exploitation attempts against the vulnerable endpoint.
- Rotate credentials, connection strings, and secrets that may have been stored in files accessible to the application.
Patch Information
No vendor patch or advisory is currently available. According to the disclosure, the vendor was contacted early but did not respond. Organizations should monitor the VulDB vulnerability record for updates and contact PMWeb support directly for remediation guidance.
Workarounds
- Block or filter requests to downloader.aspx at the reverse proxy or WAF until a vendor fix is released.
- Run the IIS application pool identity under a least-privilege account with read access limited to required directories.
- Apply file system ACLs that prevent the application pool from reading sensitive OS and configuration files outside its working directory.
- Enable IIS Request Filtering to reject requests containing .. sequences and disallowed characters in query parameters.
# Example IIS Request Filtering configuration in web.config
<configuration>
<system.webServer>
<security>
<requestFiltering allowDoubleEscaping="false">
<denyQueryStringSequences>
<add sequence=".." />
<add sequence="%2e%2e" />
<add sequence=":\" />
</denyQueryStringSequences>
</requestFiltering>
</security>
</system.webServer>
</configuration>
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

