CVE-2026-78381
Received Received - Intake

Path Traversal in RansomLook Group Posts

Vulnerability report for CVE-2026-78381, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: CIRCL

Description

RansomLook contains a path traversal vulnerability in the handling of the screen field associated with group posts. The GroupPost.get API handler concatenates the database-controlled screen value directly with the application's source/ directory and opens the resulting path without verifying that the resolved file remains within the intended directory. Because the screen field is free-form and can be populated either through the administrative post editor or through data imported from a remote RansomLook instance, a malicious upstream instance can provide traversal sequences such as ../config/generic.json. When the affected post is subsequently retrieved through the API, RansomLook resolves and reads the attacker-controlled path and returns the contents of the referenced file Base64-encoded in the API response. This can allow an attacker (being admin) controlling imported post data to read arbitrary files accessible to the RansomLook process, potentially exposing sensitive configuration data, API credentials, password hashes, or other application secrets. The attack does not require the malicious upstream to possess an account on the affected RansomLook instance. The vulnerability is addressed by resolving screen paths with os.path.realpath() and verifying that the resolved path remains beneath the application's source/ directory. Validation is performed both when values are written and immediately before files are read. Using canonical paths also prevents traversal through symbolic links that would bypass purely lexical path normalization checks.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ransomlook ransomlook *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

RansomLook has a path traversal vulnerability in the screen field of group posts. The API handler combines the screen value directly with the application's source directory without checking if the final path stays within that directory. Attackers can use sequences like ../config/generic.json to read arbitrary files accessible to the RansomLook process, such as configuration data or credentials. The issue occurs because the screen field can be set by an admin or imported from a remote instance, and the path is not validated before file access.

Detection Guidance

Check for unusual file reads in logs, especially Base64-encoded responses containing sensitive files. Inspect API responses for the 'screen' field in posts, looking for path traversal sequences like '../'. Monitor for unauthorized access to configuration files or secrets.

Impact Analysis

An attacker with admin access or control over imported post data could read sensitive files on the server, including configuration files, API credentials, password hashes, or other secrets. This could lead to further compromise of the application or the underlying system, depending on the exposed data.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements such as GDPR (data protection) or HIPAA (health information privacy). Exposure of personal or confidential data may result in legal penalties, reputational damage, and loss of trust.

Mitigation Strategies

Apply the patch from the RansomLook commit (274faccf65898e88ef54f35f304e0821a852a0b8) which validates paths using os.path.realpath(). Ensure the 'screen' field is sanitized both when writing and reading. Restrict file permissions to limit access to sensitive directories.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78381. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart