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

New CVE Detected

CVE-2026-76195 – Unauthenticated Remote Code Execution (OS Command Injection) – Adobe Campaign Class

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

Summary

CVE-2026-76195 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 application. The flaw carries the maximum CVSS v3.1 score of 10.0, requires no privileges or user interaction, and affects fully on-premise ACC deployments as well as the on-premise components of hybrid deployments. It was disclosed by Adobe on August 25, 2026 as part of security bulletin APSB26-134, alongside several other critical vulnerabilities in the same product (including a related OS command injection issue, CVE-2026-76197, and an SSRF issue, CVE-2026-76193).

Technical details

  • Root cause: Improper neutralization of special elements used in an OS command (CWE-78) within Adobe Campaign Classic, allowing attacker-supplied input to be passed to and executed by the underlying operating system shell.
  • Trigger conditions: No authentication or user interaction is required to trigger the vulnerability; the flaw is reachable over the network.
  • Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: Successful exploitation results in arbitrary code execution in the context of the current user running the ACC process, with high impact to confidentiality, integrity, and availability, and a changed scope (S:C), meaning the impact can extend beyond the vulnerable component itself.
  • Deployment scope: Adobe notes this bulletin applies only to fully on-premise Adobe Campaign Classic deployments and the on-premise components of hybrid deployments; Adobe-hosted instances have already been remediated and require no customer action.

Affected software

  • Adobe Campaign Classic (ACC) v7: build 9400 and earlier (Windows and Linux)

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
  • Adobe Priority Rating: 1 (highest — exploitation likely, patch immediately)

Mitigation and recommended actions

  • Immediate: Upgrade on-premise Adobe Campaign Classic v7 installations (Windows and Linux) to build 9401 or later, as detailed in Adobe’s official release notes referenced in APSB26-134.
  • Hybrid deployments: Apply the same on-premise patch to the on-premise components; Adobe has already remediated the Adobe-hosted portions of hybrid environments.
  • If immediate patching is not possible: Restrict network access to Adobe Campaign Classic management and application interfaces to trusted internal networks/VPNs only, and closely monitor logs for anomalous process execution or command-injection indicators until the patch can be applied. Adobe has not published a workaround in lieu of patching, so upgrading remains the only fully effective remediation.

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