Skip to main content
Mallory
MediumVulnerability

CVE-2026-73140: Private evaluation comments disclosure in cti-transmute evaluation report exports

Published Aug 11, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v4
EPSS0.35%29th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-73140CWE-862 · Missing Authorization

CVE-2026-73140 is an authorization flaw in cti-transmute affecting versions 1.4 and earlier. When generating evaluation report exports, the report-building logic did not enforce the same comment-level access-control checks used during normal comment retrieval. Specifically, build_evaluation_report() included all evaluation comments for a conversion without applying visibility, privacy, ownership, authorship, and administrative privilege checks. As a result, a user who was permitted to view a conversion could export its evaluation report in Markdown or PDF form and receive private evaluation comments that should have been restricted to the conversion owner, the comment author, or an administrator. The exported data also exposed the comment author's name.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in unauthorized disclosure of private evaluation comments associated with a conversion, along with the corresponding author names. This breaks comment confidentiality boundaries and allows a user with conversion-view access to obtain sensitive evaluation content that should remain limited to the conversion owner, the comment author, or an administrator.

Mitigation

If you can’t patch tonight, do this now.

Until the fix is deployed, restrict access to conversion viewing and evaluation report export functionality to only highly trusted users, and avoid distributing Markdown or PDF evaluation report exports that may contain comments. Review existing exported reports for unintended disclosure of private evaluation comments and author identities.

Remediation

Patch, then assume compromise.

Upgrade to cti-transmute 1.5 or later. The fix modifies report generation so the requesting user is passed into the report builder and each evaluation comment is filtered through the shared access.can_see_comment() authorization function before inclusion in the exported report.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-73140 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-73140 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-73140?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-73140.
Is there a patch for CVE-2026-73140?
Upgrade to cti-transmute 1.5 or later. The fix modifies report generation so the requesting user is passed into the report builder and each evaluation comment is filtered through the shared access.can_see_comment() authorization function before inclusion in the exported report.
How severe is CVE-2026-73140?
CVE-2026-73140 has a CVSS v4 score of 5.3 (Medium) and an EPSS score of 0.35% (29th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.