In affected versions of MISP cti-transmute, the conversion-history details endpoint performs an incomplete authorization check. When a history record references a deleted conversion, the associated conversion lookup returns None. The previous logic only denied access when the conversion object existed and the visibility check failed. As a result, deleted conversions bypassed the authorization check and their retained history input/output could be disclosed to a user able to request the corresponding history entry. The July 22, 2026 commit changes the logic to deny access whenever the conversion is missing or the requester lacks permission
CVE-2026-72759
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
August 10, 2026
Advisory Details (1)
Auto-updated Aug 10, 2026commit 88dc65f0117c (MISP/cti-transmute)
Fix landed in MISP/cti-transmute commit 88dc65f0117c — awaiting tagged release
https://github.com/MISP/cti-transmute/commit/88dc65f0117cf7a120f6252674c529e7b9c9b8c3Vendor Advisories for CVE-2026-72759(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 38× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:54 UTCGHSA enrichment
- 2026-08-19 20:57 UTCEG score recompute
- 2026-08-19 20:57 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:00 UTCEG score recompute
- 2026-08-18 22:59 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 01:02 UTCEG score recompute
- 2026-08-18 01:02 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:05 UTCEG score recompute
- 2026-08-17 03:05 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:07 UTCEG score recompute
- 2026-08-16 05:07 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 07:10 UTCEG score recompute
- 2026-08-15 07:10 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 09:12 UTCEG score recompute
- 2026-08-14 09:12 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
Show 13 moreShow fewer
- 2026-08-13 11:14 UTCEG score recompute
- 2026-08-13 11:14 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 13:17 UTCGHSA enrichment
- 2026-08-11 15:19 UTCEG score recompute
- 2026-08-11 15:19 UTCGHSA enrichment
- 2026-08-10 17:22 UTCEG score recompute
- 2026-08-10 17:22 UTCGHSA enrichment
- 2026-08-10 17:10 UTCEG score recompute
- 2026-08-10 17:10 UTCGHSA enrichment
- 2026-08-10 15:29 UTCEG score recompute
- 2026-08-10 14:35 UTCEG score recompute
- 2026-08-10 14:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-72759?
When was CVE-2026-72759 disclosed?
Is CVE-2026-72759 actively exploited?
What is the CVSS score of CVE-2026-72759?
How do I remediate CVE-2026-72759?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72759
Is Your Infrastructure Affected by CVE-2026-72759?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.