CVE-2026-78555: RansomLook API Key Disclosure Through /admin/apikeys HTML Source
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.
Security readout for executives and security teams
Plain-English summary
RansomLook’s administration page visually shortened API keys but still placed complete credentials in the page’s HTML. Anyone or any system able to capture that authenticated response could recover the keys and use their assigned privileges, potentially including private-data access. The supplied record rates this critical, but public evidence of active exploitation is not provided.
Executive priority
Treat as an immediate credential-containment issue for any RansomLook deployment where administrators accessed this page before patching. Patch promptly, rotate exposed keys, and investigate response-retaining systems and API activity. Priority remains critical because stolen keys may expose or modify data, despite no supplied evidence of active exploitation.
Technical view
The authenticated /admin/apikeys response embedded full API tokens in hidden action fields, creating credential disclosure through the DOM, source, caches, proxies, monitoring, or debugging systems. The cited patch replaces rendered tokens with SHA-256-derived opaque handles resolved server-side and limits full-key display to initial creation.
Likely exposure
Exposure applies to unpatched RansomLook deployments whose authenticated /admin/apikeys responses contained existing keys. Risk increases where administrators visited the page or response bodies were cached, logged, monitored, or proxied. The supplied affected-version data is unclear, so exact vulnerable release boundaries cannot be established from these sources.
Exploitation context
The CVE is not listed as KEV in the supplied record, and no cited source reports active exploitation. Initial disclosure requires access to the authenticated administration response, reflected by PR:H in the CVSS vector. A recovered token could then be used according to that key’s configured privileges.
Researcher notes
The record maps the issue to CWE-200 and CWE-522 and assigns CVSS 4.0 score 9.4. The patch design removes secrets from subsequent HTML rendering and substitutes server-resolved handles. The affected entry lists version “0” with default status “unaffected,” leaving product-version scope ambiguous; validate release ancestry directly against the cited commit.
Mitigation direction
Apply the vendor patch or a release containing commit b358dfa4f40c677a47c602ebbb4473aeae349f5c.
Rotate every API key that may have appeared on the vulnerable administration page.
Review and securely purge captured response bodies from caches, proxies, debugging tools, and monitoring systems.
Restrict administration-page access and minimize systems permitted to retain authenticated response content.
Validation and detection
Confirm full API keys are absent from the patched page source, DOM, and action submissions.
Verify administrative actions submit opaque handles that the server resolves without returning the token.
Confirm newly created keys are disclosed only once and omitted from later page rendering.
Review API authentication and private-data access records for unexpected activity using affected keys.
Identify which RansomLook release contains the cited patch; supplied version boundaries are insufficient.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.