PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-75721 Adobe CVE debrief

CVE-2026-75721 is a critical vulnerability in Adobe Campaign Classic that could allow arbitrary code execution. Defenders should assess exposure, prioritize remediation, and verify affected versions. The vulnerability is caused by an Improper Control of Generation of Code ('Code Injection') and has a CVSS score of 10. Exploitation does not require user interaction and could result in arbitrary code execution in the context of the current user. Defenders should review and apply vendor-provided patches, and verify inventory of Adobe Campaign Classic deployments.

Vendor
Adobe
Product
Adobe Campaign Classic
CVSS
CRITICAL 10
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-22
Original CVE updated
2026-09-26
Advisory published
2026-09-22
Advisory updated
2026-09-26

Who should care

Defenders of Adobe Campaign Classic instances should assess exposure and prioritize remediation due to the critical severity and potential for arbitrary code execution. This includes operators, administrators, and security teams responsible for the deployment and maintenance of Adobe Campaign Classic. Defenders should review and apply vendor-provided patches, and verify inventory of Adobe Campaign Classic deployments to mitigate the vulnerability.

Why it matters

CVE-2026-75721 is a critical vulnerability in Adobe Campaign Classic that could allow arbitrary code execution. Defenders should assess exposure, prioritize remediation, and verify affected versions.

  • Potential for arbitrary code execution in the context of the current user
  • Critical severity with CVSS score of 10
  • Exploitation does not require user interaction

Technical summary

Adobe Campaign Classic is affected by an Improper Control of Generation of Code ('Code Injection') vulnerability that could result in arbitrary code execution in the context of the current user. The vulnerability has a CVSS score of 10 and is considered critical. Exploitation does not require user interaction. Defenders should review and apply vendor-provided patches, and verify inventory of Adobe Campaign Classic deployments to mitigate the vulnerability. The vulnerability could allow an attacker to execute arbitrary code, potentially leading to a compromise of the affected system.

Defensive priority

High

Recommended defensive actions

  • Assess exposure of Adobe Campaign Classic instances
  • Prioritize remediation of affected versions
  • Verify inventory of Adobe Campaign Classic deployments
  • Review and apply vendor-provided patches
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its critical severity and potential for arbitrary code execution. The CVE record was published on 2026-09-22T18:17:16.033Z and has not been modified since then. The NVD entry provides additional information on the vulnerability, including its CVSS score and potential impact. Defenders should review these sources to understand the vulnerability and its potential impact.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-75721 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-75721

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-75721 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75721

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.