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

Back
New CVE Detected

CVE-2026-76197 – OS Command Injection / Unauthenticated RCE – Adobe Campaign Classic v7 ≤ 7.4.4 buil

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76197 is a critical OS Command Injection vulnerability (CWE-78) in Adobe Campaign Classic (ACC) that allows an unauthenticated, remote attacker to execute arbitrary code in the context of the user running the application. The flaw requires no user interaction and carries the maximum CVSS v3.1 base score of 10.0, making it one of the most severe classes of vulnerability affecting internet-exposed marketing automation infrastructure. It affects only fully on-premise deployments of Adobe Campaign Classic and the on-premise components of hybrid deployments; Adobe-hosted instances have already been remediated.

Technical details

  • Root cause: Improper neutralization of special elements used in an OS command (CWE-78) — user-supplied input reaches a system-level command execution path without adequate sanitization, allowing injection of arbitrary shell commands.
  • Trigger conditions: No authentication or privileges are required to trigger the flaw, and no user interaction is needed.
  • Attack vector: Network — the vulnerability is remotely exploitable over the network against an on-premise ACC instance.
  • Impact: Successful exploitation results in arbitrary code execution in the context of the current user; the CVSS vector reflects a scope change (S:C) with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H), indicating the attacker can affect resources beyond the vulnerable component itself.
  • Adobe has stated it is not aware of any active exploitation of this issue in the wild as of the advisory’s publication.

Affected software

  • Adobe Campaign Classic (ACC) v7: build 9400 and earlier (version 7.4.4 build 9400 and earlier), on both Windows and Linux platforms
  • Applies only to fully on-premise ACC deployments and the on-premise components of hybrid deployments (Adobe-hosted/managed instances have already been remediated by Adobe and require no customer action)

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 all on-premise Adobe Campaign Classic v7 deployments to build 9401 (ACC v7: 7.4.4 build 9401) or later, as released by Adobe in security bulletin APSB26-134.
  • If immediate patching is not possible: Restrict network access to the Adobe Campaign Classic management/application interfaces to trusted internal networks or VPN only, and monitor for anomalous process execution or unexpected outbound connections from the ACC host as an interim compensating control until the patch can be applied.
  • Confirm that any hybrid deployment’s on-premise components are also updated, since Adobe-hosted portions of hybrid environments are already remediated but on-premise portions are not.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge