Skip to main content
Mallory
HighVulnerability

CVE-2026-69079: Unauthenticated DoS in CTI-Transmute activity timeline

Published Aug 3, 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.
CVSS8.7High · v4
EPSS0.54%46th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-69079CWE-770 · Allocation of Resources Without…

CVE-2026-69079 is a high-severity uncontrolled resource-consumption vulnerability in CTI-Transmute affecting versions up to and including 1.4.0. The flaw exists in the unauthenticated activity timeline endpoint, which accepts a user-controlled days query parameter without enforcing a reasonable upper bound. By supplying an excessively large value, a remote attacker can cause the application to retrieve and process activity data across an arbitrarily large time range. This results in disproportionate backend work and can exhaust database, CPU, or memory resources. The issue is classified as CWE-770 because resource allocation and processing were not properly limited or throttled for attacker-controlled input.

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 enables unauthenticated denial of service against the CTI-Transmute application. A single crafted request can trigger excessive processing, slowing or delaying concurrent requests and potentially causing internal server errors. Repeated requests can further degrade service availability and may render the website partially or fully unavailable. The documented impact is on availability; no direct confidentiality or integrity impact is indicated.

Mitigation

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

If immediate upgrade is not possible, enforce strict server-side bounds on the activity timeline range accepted by the endpoint, rejecting or normalizing excessively large values for the days parameter. Additional defensive measures can include rate limiting unauthenticated requests to the affected endpoint, monitoring for abnormal resource consumption, and placing the service behind infrastructure controls that can absorb or block repeated abusive requests.

Remediation

Patch, then assume compromise.

Upgrade to CTI-Transmute 1.5 or later, which fixes the vulnerability by clamping the requested timeline range to a minimum of 1 day and a maximum of 1,095 days. Ensure equivalent server-side validation is applied anywhere similar user-controlled range parameters are accepted, and verify the patched deployment under load after upgrade.

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-69079 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-69079 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-69079?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-69079.
Is there a patch for CVE-2026-69079?
Upgrade to CTI-Transmute 1.5 or later, which fixes the vulnerability by clamping the requested timeline range to a minimum of 1 day and a maximum of 1,095 days. Ensure equivalent server-side validation is applied anywhere similar user-controlled range parameters are accepted, and verify the patched deployment under load after upgrade.
How severe is CVE-2026-69079?
CVE-2026-69079 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.54% (46th percentile) as of Sep 25, 2026.
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 activity1Community discussion across Reddit, Mastodon, and other social sources.