Act nowDisclosed

Advisory · CVE-2026-106619

Input validation flaw in ColdFusion leads to code execution

ColdFusion improperly validates input in a path that can result in arbitrary code execution, though Adobe's vector requires high attack complexity. Adobe rates it CVSS 3.1 9.0.

Advisory published October 13, 2026Independent summary
Vendor
Adobe
Product
ColdFusion
Identifier / CWE
CVE-2026-106619
CWE-20
Action timing
Immediate
ELI5

Explain it like I’m five

Input the server should have turned away is instead accepted and steered into code execution, even if the path there is fiddly.

SIMPLIFIED_ATTACK_PATH03 STEPS
  1. 01Reach ColdFusion

    An attacker sends requests to a ColdFusion server.

  2. 02Flaw engaged

    The vulnerable function processes the attacker's input without the control it needed.

  3. 03Code executes

    Arbitrary code runs in the context of the ColdFusion service user.

What happened

Adobe disclosed CVE-2026-106619 in bulletin APSB26-144: an improper input validation vulnerability (CWE-20) in ColdFusion that could result in arbitrary code execution; Adobe’s vector notes high attack complexity and no privileges required.

Adobe lists the affected ColdFusion releases in APSB26-144 (the NVD record names the 2023 update line through 2023.0.25, with 2023.0.26 listed as unaffected). Apply the update Adobe provides for your release line.

What to do

  1. Inventory every ColdFusion deployment, including test, training, and individually managed instances.
  2. Apply the vendor fix or upgrade exactly as directed in the linked vendor bulletin or advisory.
  3. Restrict network access to ColdFusion while remediation is underway, especially for internet-facing instances.
  4. Review application and server logs for malformed requests in ColdFusion logs and application errors clustered around specific endpoints.
  5. Check for accounts, content, or configuration created outside normal change processes, and rotate exposed credentials where access cannot be ruled out.
  6. Verify the deployed version or patch level after remediation.

Management note

High complexity lowers the odds, not the impact. It rides along with the same APSB26-144 update, so there is no reason to leave it behind.