RansomLook does not consistently
enforce authorization checks when accessing groups, markets, and ransom
notes marked as private. An unauthenticated or otherwise unauthorized
remote attacker can access information associated with private entities
through several web views and API endpoints.
The affected functionality can
disclose private group or market names, ransom-note content, and
metadata associated with private groups. The /compare
functionality can also be queried directly with the name of a private
entity, allowing an unauthorized user to retrieve information such as
post counts, mirror totals, and uptime even when the entity is excluded
from the normal user interface. The patch explicitly adds a privacy
check before returning this information.
Ransom-note views, search results,
and API endpoints were similarly missing consistent filtering. The fix
introduces normalized private-group identifiers and alias handling, then
rejects or filters notes associated with private groups before
returning them to unauthorized callers.
An attacker can exploit the issue
remotely without authentication or user interaction, resulting in
disclosure of information that was explicitly intended to be restricted
to authorized users.
0.7%(unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-78372 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78372?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78372?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-78372 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.