Adobe patches 18 critical Campaign Classic flaws
Free public brief. The indicators, the detections with Splunk and KQL already written, and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Adobe fixed 18 critical vulnerabilities in Campaign Classic, including 8 CVSS 10.0 unauthenticated RCE bugs; NCSC-NL urges upgrade to 7.4.4 build 9402.
NCSC-NL published an advisory summarizing Adobe's patch for 18 critical vulnerabilities in Adobe Campaign Classic, a marketing automation platform. The flaws span OS command injection, SQL injection, code injection, incorrect authorization, and Server-Side Request Forgery (SSRF). Ten of the eighteen vulnerabilities can be exploited remotely without authentication, and eight of these (CVE-2026-82004, CVE-2026-73369, CVE-2026-84412, CVE-2026-89275, CVE-2026-75723, CVE-2026-75699, CVE-2026-75703, CVE-2026-75721) carry the maximum CVSS score of 10.0, requiring no authentication or user interaction. Seven of these are noted by Adobe as capable of arbitrary code execution; CVE-2026-75703 is noted for Denial-of-Service impact.
Successful exploitation across the full set of vulnerabilities could result in arbitrary code execution, privilege escalation, security control bypass, arbitrary file read, and denial of service. Adobe-hosted (cloud) environments have already been patched by Adobe; self-hosted/on-premises customers must apply the update themselves. No evidence of in-the-wild exploitation is mentioned in this advisory, but given the unauthenticated, zero-click nature of multiple critical RCE flaws, defenders running self-managed Adobe Campaign Classic instances should prioritize patching.
Remediation: update Adobe Campaign Classic to version 7.4.4 build 9402. Defenders should verify patch status of any on-premises deployments immediately, monitor for anomalous authentication-free requests to Campaign Classic endpoints, and review logs for signs of command/SQL injection or SSRF attempts pending confirmation of patch application.
Mentioned in this report
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0393.html
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections with the Splunk SPL and Microsoft KQL already written, the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 9,756 reports from 155 sources, 1,546 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs