Quick answers
- Is CVE-2026-78381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78381 being exploited in the wild.
- How severe is CVE-2026-78381?
- Informational severity, published 24 August 2026.
- Which products and versions are affected?
- RansomLook <UNKNOWN>.
- Is there a fix for CVE-2026-78381?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78381 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-78381?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
RansomLook's GroupPost.get API handler concatenates a database-controlled screen field value directly with the application's source/ directory and opens the resulting file without path validation. The screen field is free-form and can be populated through the administrative editor or imported from a remote RansomLook instance. An attacker controlling upstream instance data can inject path traversal sequences (e.g., ../config/generic.json) that, when the post is retrieved via API, cause the application to read and return the file contents Base64-encoded. The vulnerability requires administrative privileges but can be exploited through data imported from a malicious upstream instance without requiring an account on the target. The fix validates resolved paths using os.path.realpath() to ensure they remain within the source/ directory, applied both at write and read time, preventing symbolic link traversal attacks.
Affected products
- RansomLook <UNKNOWN>
Timeline
- 2026-08-24: disclosed