Skip to main content
Mallory
MediumVulnerability

CVE-2026-73155: Missing authorization in CTI-Transmute comment reactions

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-73155CWE-862 · Missing Authorization

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.

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 allows an authenticated attacker to bypass comment-level access controls and modify reaction state on comments they are not permitted to view. This results in unauthorized alteration of comment metadata and undermines the integrity of access-restricted discussion content. The issue is an authorization bypass rather than direct disclosure of comment contents, but it demonstrates and exploits a failure to enforce object-level permissions on a protected resource.

Mitigation

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

No dedicated workaround is documented. Until the fixed release is deployed, reduce exposure by restricting access to comment reaction functionality to trusted users where operationally feasible, monitoring for anomalous reaction activity on restricted comments, and limiting opportunities for users to enumerate or infer comment identifiers. The primary mitigation is prompt upgrade to the patched version.

Remediation

Patch, then assume compromise.

Upgrade CTI-Transmute to version 1.5 or later. The corrected implementation fetches the target comment, rejects missing or deleted comments, retrieves the associated conversion, and enforces an authorization check to confirm that the current user is permitted to see the comment before toggling reactions. Unauthorized requests should be rejected with HTTP 403.

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-73155 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-73155 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-73155?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-73155.
Is there a patch for CVE-2026-73155?
Upgrade CTI-Transmute to version 1.5 or later. The corrected implementation fetches the target comment, rejects missing or deleted comments, retrieves the associated conversion, and enforces an authorization check to confirm that the current user is permitted to see the comment before toggling reactions.
How severe is CVE-2026-73155?
CVE-2026-73155 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.