Koffei

CVE-2026-42589

🟠 Medium

Gotenberg (stateless PDF conversion API, default port 3000). Detection note: the endpoint answers HTTP 200 with a valid PDF, so anything monitoring status codes sees nothing · < 8.31.0. The sources diverge: the GitHub advisory names 8.29.1 as the then-default for the :8 tag and one write-up gives the exploited range as 8.17.0 to 8.30.1 ; use < 8.31.0 for triage

CVSS (Koffei note)
9.8
CVSS (v3.1, CVE List)
9.8
EPSS (2026-11-18)
3.013%
87.68th percentile

Exploitation

Yes — mass-exploited on 31/08/2026, though not in CISA KEV and the record's SSVC still reads exploitation poc with a May timestamp and has not been touched since, so Vulnrichment-based triage underrates this badly. One documented campaign: 54 minutes, 206 targets, 198 confirmed exploited (96.6%) across 196 IPs, 184 callbacks and roughly 150 verified miner installs. Payload was stock XMRig 6.26.0, persistence in /tmp/polkitd/ plus a root systemd-polkitd.service with /usr/bin/polkitd.d/, operator host 107.175.69.137 on ports 18888, 19999 and 13337, with two shared MoneroOcean pools that should be hunted rather than blocklisted. No named actor ; the malware is commodity. Source caveat: this rests on a single independent researcher working from the operator's own recovered scripts, logs and target lists cross-checked against captured traffic, not on a vendor or CERT, and whether exploitation continued past 31/08/2026 is not known. Re-tested on 06/11/2026: the campaign of 31/08/2026 is 67 days old, outside the 60-day window, so this row is demoted 🔴 → 🟠. Nothing read in this re-check dates exploitation after 07/09/2026. The flaw is still exploited-in-the-wild history with a patch available ; what changed is the age of the evidence, not the facts. A search for later Gotenberg exploitation returned only vulnerability-database aggregators and no incident reporting, and the record is unchanged since 14/05/2026, still no KEV entry and still SSVC poc. The single-source caveat below therefore stands unresolved. There was never a gap between disclosure and weaponisation: the vendor advisory itself publishes working PoC material, and a public chained-exploit repository also exists

Timeline

  1. 14/05/2026CVE record published (CVE List)
  2. 30/10/2026ThreatsDay roundup — additional exploited CVEs

Risk

9.8 Critical (v3.1, GitHub CNA) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, EPSS 3.013% (87.47th percentile, unchanged when re-scored 05/11/2026) (CWE-78 : the /forms/pdfengines/metadata/write endpoint passes JSON metadata keys to ExifTool without character validation, so a newline in a key splits the argument stream and lets an attacker inject ExifTool flags, notably -if, which evaluates Perl. One unauthenticated HTTP request gives OS command execution as the Gotenberg user)

Fix

Yes — 8.31.0 (released 17/04/2026), which strips control characters and line breaks from the endpoint and drops System:-prefixed tags. The upgrade has teeth beyond the CVE: the release notes never mention this CVE or the advisory ID ; dropping System: tags is a breaking change ; the same release ships breaking SSRF hardening plus a default webhook deny-list covering loopback, RFC1918, link-local and IPv6 ULA, so a deployment that uses internal addresses breaks on upgrade unless the override flags are set first ; and thecodingmachine/gotenberg images are no longer published, so pull gotenberg/gotenberg. A companion advisory covers the same injection class in the underlying go-exiftool library, so fixing Gotenberg does not fix other consumers

Official description

Gotenberg is a Docker-powered stateless API for PDF files. Prior to 8.31.0, Gotenberg's /forms/pdfengines/metadata/write HTTP endpoint accepts a JSON metadata object and passes its keys directly to ExifTool via the go-exiftool library. No validation is performed on key characters. A \n embedded in a JSON key splits the ExifTool stdin stream into a new argument line, allowing an attacker to inject arbitrary ExifTool flags — including -if, which evaluates Perl expressions. This achieves unauthenticated OS command execution in a single HTTP request. The response is HTTP 200 with a valid PDF, making the attack transparent to basic monitoring. This vulnerability is fixed in 8.31.0.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE-78