CVE-2026-78555
RansomLook API Key Disclosure Through /admin/apikeys HTML Source
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.
INFO
Published Date :
Aug. 24, 2026, 8:17 p.m.
Last Modified :
Oct. 12, 2026, 9:10 p.m.
Remotely Exploit :
Yes !
Source :
5a6e4751-2f3f-4070-9419-94fb35b644e8
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 4.0 | CRITICAL | 5a6e4751-2f3f-4070-9419-94fb35b644e8 | ||||
| CVSS 4.0 | CRITICAL | 5a6e4751-2f3f-4070-9419-94fb35b644e8 |
Solution
- Update the application to remove API keys from page rendering.
- Replace full API keys with opaque handles.
- Resolve handles server-side for administrative actions.
- Ensure keys are disclosed only at creation.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-78555.
| URL | Resource |
|---|---|
| https://github.com/RansomLook/RansomLook/commit/b358dfa4f40c677a47c602ebbb4473aeae349f5c |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-78555 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-78555
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-78555 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-78555 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 12, 2026
Action Type Old Value New Value Added Translation Title: Ransomlook, Description: RansomLook expuso claves API completas en el código fuente HTML de la página de administración autenticada /admin/apikeys. Aunque la interfaz mostraba solo una representación abreviada de cada clave, el token completo estaba incrustado en campos de formulario ocultos utilizados por las acciones de habilitar/deshabilitar, acceso privado y eliminar. Como resultado, las credenciales de la API podían recuperarse inspeccionando el código fuente de la página o el DOM. Las credenciales también podían exponerse involuntariamente a través de componentes que retienen o inspeccionan los cuerpos de respuesta HTTP, como proxies de depuración, cachés del navegador, sistemas de monitoreo u otros intermediarios. Un atacante que obtuviera uno de estos tokens podría autenticarse posteriormente utilizando los privilegios asignados a esa clave, incluyendo el acceso a datos privados donde a la clave se le habían otorgado dichos permisos. El parche elimina las claves API de la renderización de páginas subsiguientes y las reemplaza con identificadores opacos derivados de SHA-256. Las acciones administrativas envían solo estos identificadores, los cuales se resuelven de nuevo al token correspondiente en el servidor. La clave API completa se divulga, por lo tanto, solo una vez, cuando se crea inicialmente. -
New CVE Received by 5a6e4751-2f3f-4070-9419-94fb35b644e8
Aug. 24, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://github.com/RansomLook/RansomLook/', 'vendor': 'ransomlook', 'product': 'ransomlook', 'versions': [{'status': 'affected', 'version': '0', 'versionType': 'patch', 'lessThanOrEqual': '2.0.0'}], 'defaultStatus': 'unaffected'}] Added 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. Added CVSS V4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CWE CWE-200 Added CWE CWE-522 Added Reference https://github.com/RansomLook/RansomLook/commit/b358dfa4f40c677a47c602ebbb4473aeae349f5c -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 24, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-78555', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-24T20:05:27.595241Z'}