CVE-2026-73155 is an authorization flaw in CTI-Transmute affecting versions 1.4 and earlier. The comment reaction handler accepted an attacker-controlled comment identifier and passed it to the reaction-toggling logic after only checking that the identifier was syntactically valid and that the requested emoji was allowed. It did not verify whether the requesting authenticated user was authorized to view the target comment. As a result, comment-level visibility restrictions were not enforced for reaction operations. A user who could determine the identifier of a private, deleted, or otherwise inaccessible comment could add or remove emoji reactions on that comment despite lacking permission to access it. The fix retrieves the target comment, rejects missing or deleted comments, resolves the associated conversion object, and enforces a comment visibility authorization check before allowing the reaction change.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.