Skip to main content
Mallory
MediumVulnerability

CVE-2026-72759: Authorization bypass in MISP cti-transmute conversion-history details endpoint

Published Aug 10, 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.
CVSS6.9Medium · v4
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-72759CWE-863

CVE-2026-72759 is an authorization flaw in affected versions of MISP cti-transmute, including versions 1.4 and earlier, in the conversion-history details endpoint. The endpoint performs an incomplete authorization check when serving retained history data for conversions. If a history record references a conversion that has since been deleted, the associated conversion lookup returns no object. The vulnerable logic only denied access when the conversion object existed and the visibility check failed. When the conversion was missing, the authorization path was effectively bypassed, allowing the endpoint to return retained history input and output associated with the deleted conversion. This results in disclosure of private conversion content to a user able to request the corresponding history entry.

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 unauthorized disclosure of retained conversion-history data, specifically the stored input and output associated with deleted conversions. The issue does not require code execution; its primary impact is exposure of private conversion content that should no longer be accessible to users lacking permission. Depending on the sensitivity of converted threat-intelligence material, this may reveal confidential data handled by the platform.

Mitigation

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

If immediate patching is not possible, restrict access to conversion-history detail functionality to the smallest possible set of trusted users, review and limit which users can enumerate or request history entries, and remove or minimize retention of conversion-history input/output for deleted conversions where operationally feasible. Additional compensating controls include monitoring for unusual access to history-detail endpoints and enforcing stricter application-layer authorization checks through custom controls or reverse-proxy policy where available. Information on a vendor-supported mitigation beyond patching is currently not available.

Remediation

Patch, then assume compromise.

Upgrade to MISP cti-transmute 1.5 or another patched release containing the July 22, 2026 fix. The fix changes the authorization logic in the conversion-history details endpoint to deny access whenever the associated conversion record is missing or the requester lacks permission. Verify that all deployments running 1.4 or earlier are updated and that regression tests covering deleted-conversion history access are present in the deployed codebase.

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-72759 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-72759 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-72759?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-72759.
Is there a patch for CVE-2026-72759?
Upgrade to MISP cti-transmute 1.5 or another patched release containing the July 22, 2026 fix. The fix changes the authorization logic in the conversion-history details endpoint to deny access whenever the associated conversion record is missing or the requester lacks permission.
How severe is CVE-2026-72759?
CVE-2026-72759 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.48% (42nd 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.