Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-75699 – Unauthenticated Remote Code Execution – Adobe Campaign Classic ≤ 7.4.4 build 9401

Be the first to know when new zero-days emerge:

Summary

CVE-2026-75699 is a critical Code Injection vulnerability (CWE-94: Improper Control of Generation of Code) affecting Adobe Campaign Classic (ACC). The flaw allows an attacker to achieve arbitrary code execution in the context of the current user, and can be exploited remotely over the network without authentication or any user interaction. Adobe rated the issue at the maximum CVSS v3.1 base score of 10.0 and addressed it in security bulletin APSB26-142, released as part of its September 2026 Patch Tuesday updates.

Technical details

  • Root cause: Improper control of code generation within Adobe Campaign Classic allows attacker-supplied input to be interpreted and executed as code (CWE-94).
  • Trigger conditions: No authentication or privileges are required, and successful exploitation does not require any interaction from a victim user.
  • Attack vector: Network-based (AV:N) — an attacker can send a crafted request to a reachable/exposed Campaign Classic instance to trigger the flaw.
  • Impact: Full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H), with a changed scope (S:C), resulting in arbitrary code execution in the context of the application/current user, which can lead to complete takeover of the affected server.
  • Deployment scope: The bulletin applies to fully on-premise Adobe Campaign Classic deployments and to the on-premise components of hybrid deployments. Adobe-hosted instances were already remediated by Adobe and require no customer action.

Affected software

  • Adobe Campaign Classic (ACC) v7 — all versions up to and including 7.4.4 build 9401 (Windows and Linux) are vulnerable.

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade self-hosted Adobe Campaign Classic instances to version 7.4.4 build 9402 or later, as provided in Adobe’s APSB26-142 security bulletin.
  • If patching cannot be applied immediately: Restrict network access to Campaign Classic management/application interfaces to trusted internal networks or VPN only, and monitor exposed instances closely for anomalous activity until the patch can be applied.
  • Verification: After patching, confirm the build number reflects 7.4.4 build 9402 or higher on all on-premise nodes and hybrid-deployment on-premise components.
  • Note: Adobe-hosted Campaign Classic environments were already remediated by Adobe and do not require customer action for this issue.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge