CVE-2026-32711

pydicom is a pure Python package for working with DICOM files.

Verified by Precogs Threat Research
Last Updated: Mar 20, 2026
Base Score
7.8HIGH

Executive Summary

CVE-2026-32711 is a high severity vulnerability affecting appsec, ai-code. It is classified as Path Traversal. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"This critical flaw stems from within Pydicom, allowing a lack of rigorous type checking mechanisms. This flaw provides a direct pathway for attackers to intercept or modify sensitive data flows before they reach secure enclaves. Precogs identifies insecure data flow paths before deployment to ensure strict authentication requirements are met."

Exploit Probability (EPSS)
Low (0.0%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecai codeCWE-22

What is this vulnerability?

CVE-2026-32711 is categorized as a critical Path Traversal flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

pydicom is a pure Python package for working with DICOM files. Versions 2.0.0-rc.1 through 3.0.1 are vulnerable to Path Traversal through a maliciously cra...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score7.8 (HIGH)
Vector StringCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
PublishedMarch 20, 2026
Last ModifiedMarch 20, 2026
Related CWEsCWE-22

Impact on Systems

Sensitive File Disclosure: Unauthorized access to critical configuration files (/etc/passwd, .env files, private SSH keys).

Application Source Leak: Attackers can download proprietary source code and hardcoded credentials.

Remote Code Execution: By combining with log poisoning, attackers can write PHP/JSP shells into web-accessible directories.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Indirect References Avoid using direct file paths. Utilize indirect references (like database IDs) mapped to backend files.

2. Strict Path Resolution If direct paths are required, resolve the absolute path and rigorously verify the path starts with the expected base directory using native OS path resolving functions.

3. Chroot Jails Confine the application processes to highly restricted directory structures (chroot) with minimum readable boundaries.

Vulnerability Signature

// Vulnerable File Access
import os
def get_image(request):
    filename = request.GET.get('file')
    # VULNERABLE: No validation preventing moving upwards in the directory tree
    filepath = os.path.join('/var/www/images/', filename)
    return open(filepath, 'rb').read()

// EXPLOIT PAYLOAD: ?file=../../../../../../../../etc/passwd

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUser-supplied filename or path parameter
VectorPath manipulation using dot-dot-slash (../) sequences
SinkFile system read/write operation
ImpactUnauthorized access to sensitive files (e.g., /etc/passwd), directory traversal

Vulnerable Code Pattern

// ❌ VULNERABLE: Unvalidated path resolution
public File getFile(String filename) {
    String basePath = "/var/www/uploads/";
    // Taint sink: permits directory traversal via "../"
    return new File(basePath + filename);
}

Secure Code Pattern

// ✅ SECURE: Canonical path validation
public File getFile(String filename) throws IOException {
    File baseDir = new File("/var/www/uploads/").getCanonicalFile();
    File requestedFile = new File(baseDir, filename).getCanonicalFile();
    
    // Sanitized boundary check
    if (!requestedFile.getPath().startsWith(baseDir.getPath())) {
        throw new SecurityException("Path traversal attempt detected");
    }
    return requestedFile;
}

How Precogs Detects This

Precogs AI Analysis Engine utilizes semantic taint tracking to detect insecure path resolution sinks, ensuring file access is strictly bounded.\n

Related Vulnerabilitiesvia CWE-22

Is your system affected?

Precogs AI detects CVE-2026-32711 in compiled binaries, LLMs, and application layers — even without source code access.