PatchSiren cyber security CVE debrief
CVE-2026-76190 Adobe CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-09-08T20:18:24.157Z and has not been modified since then. The NVD entry is currently Analyzed. This Eval Injection vulnerability in Adobe ColdFusion could result in arbitrary code execution in the context of the current user. Defenders should assess exposure and apply remediation, especially in contexts where user interaction is not required for exploitation. The vulnerability has a CVSS score of 8.6 and is considered HIGH severity.
- Vendor
- Adobe
- Product
- ColdFusion 2025
- CVSS
- HIGH 8.6
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-08
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-08
- Advisory updated
- 2026-09-18
Who should care
Defenders responsible for Adobe ColdFusion installations, especially in contexts where user interaction is not required for exploitation, should assess exposure and apply remediation.
Why it matters
CVE-2026-76190 Eval Injection in Adobe ColdFusion could lead to arbitrary code execution; defenders should verify exposure, apply patches, and monitor for exploitation attempts.
- Verify exposure of ColdFusion installations to Eval Injection vulnerability.
- Apply patches to prevent potential arbitrary code execution.
- Monitor for exploitation attempts targeting this vulnerability.
- Assess the need for compensating controls due to potential scope change.
Technical summary
CVE-2026-76190 is an Eval Injection vulnerability in Adobe ColdFusion that could result in arbitrary code execution in the context of the current user. The vulnerability has a CVSS score of 8.6 and is considered HIGH severity. Exploitation does not require user interaction. The vulnerability affects Adobe ColdFusion installations, particularly versions 2023 and 2025, and their updates. Defenders should prioritize verifying exposure of ColdFusion installations to this Eval Injection vulnerability, especially in contexts where user interaction is not required for exploitation.
Defensive priority
Defenders should prioritize verifying exposure of ColdFusion installations to this Eval Injection vulnerability, especially in contexts where user interaction is not required for exploitation.
Recommended defensive actions
- Verify ColdFusion installations for exposure, especially versions 2023 and 2025, and their updates.
- Apply Adobe's official patches for the APSB26-119 advisory.
- Monitor for potential exploitation attempts targeting this vulnerability.
- Perform an asset inventory to identify all instances of Adobe ColdFusion within the organization.
- Review and implement compensating controls for exposed systems while remediation is scheduled and verified.
- Establish a process for tracking and monitoring exceptions and retesting remediated assets.
- Schedule and verify remediation through normal change control processes.
Evidence notes
The CVE and NVD records indicate an Eval Injection vulnerability in Adobe ColdFusion, potentially leading to arbitrary code execution. However, specific details about exploitation, victims, or business impact are not provided in the source corpus.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-76190 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-76190
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-76190 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76190
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://helpx.adobe.com/security/products/coldfusion/apsb26-119.html
[email protected] - Vendor Advisory
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.