CVE-2026-78555
Received Received - Intake

Information Exposure in RansomLook Admin Panel

Vulnerability report for CVE-2026-78555, 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 exposed complete API keys in the HTML source of the authenticated /admin/apikeys administration page. Although the interface displayed only a shortened representation of each key, the full token was embedded in hidden form fields used by the enable/disable, private-access, and delete actions. As a result, API credentials could be recovered by inspecting the page source or DOM. The credentials could also be unintentionally exposed through components that retain or inspect HTTP response bodies, such as debugging proxies, browser caches, monitoring systems, or other intermediaries. An attacker obtaining one of these tokens could subsequently authenticate using the privileges assigned to that key, including access to private data where the key was granted such permissions. The patch removes API keys from subsequent page rendering and replaces them with SHA-256-derived opaque handles. Administrative actions submit only these handles, which are resolved back to the corresponding token on the server. The full API key is therefore disclosed only once, when it is initially created.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-25
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-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-522 The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

RansomLook had a flaw where full API keys were exposed in the HTML source of the /admin/apikeys page. Although the interface showed shortened keys, the complete tokens were hidden in form fields used for actions like enable, disable, or delete. Attackers could retrieve these keys by inspecting the page source or through intermediaries like debugging tools or browser caches.

Detection Guidance

Check if your system runs RansomLook and inspect the HTML source of the /admin/apikeys page for hidden form fields containing full API keys. Look for tokens in browser caches, debugging proxies, or monitoring tools that may have captured HTTP responses.

Impact Analysis

If an attacker obtains an exposed API key, they can authenticate with the privileges assigned to that key. This may grant access to private data, depending on the permissions of the key. The impact includes unauthorized data access, potential data theft, or further exploitation of the system using the compromised credentials.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and access control. GDPR and HIPAA mandate strict protection of sensitive data and access credentials. Exposure of API keys could lead to unauthorized access, data breaches, and failure to meet regulatory standards for confidentiality and integrity.

Mitigation Strategies

Rotate all exposed API keys immediately. Apply the vendor patch to remove API keys from page rendering and replace them with SHA-256-derived handles. Review server logs for unauthorized access using compromised keys.

Chat Assistant

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

EPSS Chart