Description
Affected versions of MISP cti-transmute disclose users' email addresses through the account following-list endpoint. When an authenticated user follows another account, get_following() includes the followed user's email field in the API response alongside their name, user ID, and follow date. Because the email address is not required for the functionality and other related user lists omit it, an authenticated attacker could systematically follow users and collect their email addresses. The fix removes user.email from the returned object.
Published: 2026-08-10
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the MISP cti-transmute service causes the account following-list API to return the email addresses of followed users. The endpoint includes the user’s name, ID and follow date, but the email field is unnecessary for the following function. The disclosure of email addresses falls under CWE‑200, leading to a breach of user privacy and potential targetable data for malicious actors.

Affected Systems

MISP cti-transmute in all released versions that have not applied the recent commit that removes the email field from the API response. Affected users must identify whether their installation still contains the legacy get_following() implementation.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. With no EPSS score available and no listing in CISA’s KEV catalog, the risk of exploitation is likely low to moderate, depending on user access levels. Based on the description, an attacker who can authenticate to the system can repeatedly issue following requests to harvest email addresses, implying the attack vector requires legitimate credentials but no additional privileges are needed beyond normal user access.

Generated by OpenCVE AI on August 10, 2026 at 18:14 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to the latest release of cti-transmute that incorporates the commit removing user.email from the get_following() response.
  • If an upgrade cannot be performed immediately, patch the get_following() function directly to omit the user.email field from the returned object.
  • Revoke or restrict the following feature for users who do not require it, or limit the endpoint’s access to a minimum set of roles to reduce the amount of exposed data.

Generated by OpenCVE AI on August 10, 2026 at 18:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 10 Aug 2026 14:45:00 +0000

Type Values Removed Values Added
Description Affected versions of MISP cti-transmute disclose users' email addresses through the account following-list endpoint. When an authenticated user follows another account, get_following() includes the followed user's email field in the API response alongside their name, user ID, and follow date. Because the email address is not required for the functionality and other related user lists omit it, an authenticated attacker could systematically follow users and collect their email addresses. The fix removes user.email from the returned object.
Title cti-transmute Following List Exposes User Email Addresses to Authenticated Users
Weaknesses CWE-200
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-08-10T17:01:28.627Z

Reserved: 2026-08-10T14:31:48.234Z

Link: CVE-2026-72760

cve-icon Vulnrichment

Updated: 2026-08-10T17:01:24.765Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T18:15:11Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor