Skip to main content
Mallory
HighVulnerability

CVE-2026-69078: SSRF in CTI-Transmute evaluation report PDF generation

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.8High · v4
EPSS0.41%35th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-69078CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-69078 is a high-severity server-side request forgery vulnerability in CTI-Transmute’s evaluation report PDF-generation functionality affecting versions up to and including 1.4.0. User-controlled CTI content, including conversion names, descriptions, and comments, is converted from Markdown to HTML and rendered to PDF using WeasyPrint. Prior to the fix, PDF rendering relied on WeasyPrint’s default URL-fetching behavior and did not restrict the protocols or destinations that could be referenced from the generated HTML. An attacker able to supply content that is later included in an evaluation report could inject crafted resource references using schemes such as HTTP, HTTPS, or file. When the report is rendered, the application server fetches those resources using its own network reachability and filesystem privileges, enabling SSRF and local file disclosure through the rendering pipeline.

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 can allow an unauthenticated attacker to use the CTI-Transmute server as a proxy to access services reachable only from that host or its internal network, probe internal hosts and service endpoints, and retrieve local files readable by the application process. Depending on the referenced resource type and rendering context, fetched content may also be embedded into or otherwise exposed through the generated PDF. The issue therefore impacts confidentiality primarily, with limited integrity implications from attacker-controlled external fetch behavior.

Mitigation

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

If immediate upgrade is not possible, disable or tightly restrict evaluation report PDF generation for untrusted or anonymous content, and harden the rendering environment so the application process cannot reach sensitive internal services or read unnecessary local files. Constrain outbound network access from the PDF-rendering context, prevent access to local filesystem resources from the renderer, and ensure only embedded data URIs are allowed as render-time resources.

Remediation

Patch, then assume compromise.

Upgrade CTI-Transmute to version 1.5 or later. The vulnerability is fixed by replacing WeasyPrint’s default fetch behavior with a restrictive URL fetcher that permits only self-contained data URIs during PDF generation, and by removing the external Google Fonts stylesheet so report rendering performs no intentional network or filesystem fetches.

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-69078 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-69078 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-69078?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-69078.
Is there a patch for CVE-2026-69078?
Upgrade CTI-Transmute to version 1.5 or later. The vulnerability is fixed by replacing WeasyPrint’s default fetch behavior with a restrictive URL fetcher that permits only self-contained data URIs during PDF generation, and by removing the external Google Fonts stylesheet so report rendering performs no intentional network or filesystem fetches.
How severe is CVE-2026-69078?
CVE-2026-69078 has a CVSS v4 score of 8.8 (High) and an EPSS score of 0.41% (35th 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.