Skip to content
Applications

CVE-2026-27302

10.0
Critical
EPSS 0.71%Patch availableAug 12, 2026

Critical CVE-2026-27302 (CVSS 10.0): unauthenticated RCE enabling full system takeover

common questions

Is CVE-2026-27302 being exploited?

Not confirmed. CVE-2026-27302 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.71% probability of exploitation in the next 30 days.

How severe is CVE-2026-27302?

CVE-2026-27302 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-27302?

Yes. A fix has been recorded for CVE-2026-27302. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-27302 affect?

CVE-2026-27302 affects Unknown - vendor/product not disclosed, Investigate internet-facing servers and critical endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-27302?

Isolate exposed systems, enable monitoring, block exploit vectors, and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Unknown - vendor/product not disclosedInvestigate internet-facing servers and critical endpoints
impact

Unauthenticated remote code execution allowing arbitrary code execution, privilege escalation, full system compromise and data exfiltration.

action required

Immediate action required

affected versions
Adobe Adobe Campaign Classic
  • affected<= ACC v7: 7.4.3 build 9399
vendor says fixed inACC v7: 7.4.4 build 9400

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free