CVE Tools

CVE-2026-48277

ColdFusion | Improper Input Validation (CWE-20)

No known exploitation. EPSS puts it in the 70th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Adobe ColdFusion 2025Affected: ≤ 9Upgrade to: after 9Fixed builds10Stated by: CVE record
  • Adobe ColdFusion 2023Affected: ≤ 20Upgrade to: after 20Fixed builds21Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check your ColdFusion version (confirm whether you are on 2025.9 or 2023.20, or earlier).
  2. If you are affected, upgrade ColdFusion following Adobe’s remediation guidance in APSB26-68 (install the patched build specified there).
  3. After upgrading, verify the service is running the expected patched build and that any exposed public endpoints still respond normally.

Coverage timeline

4 publishers
  1. Vendor patch released

    ·watchTowr Labs summary

Sourced from public security reporting — each date is when it was published, not when it happened. 2 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction. Scope is changed.

In plain language

Written by AI from the record

Adobe ColdFusion versions 2025.9, 2023.20 and earlier have a serious input-checking flaw that can let an attacker run code on the server, so small businesses should act by upgrading using the fix from Adobe’s APSB26-68.

ColdFusion has an Improper Input Validation issue (CWE-20) where crafted input can be processed in a way that allows arbitrary code execution in the context of the current user; Adobe has a remediation in APSB26-68, but there is no confirmed CISA KEV listing or public exploit code on record.

If you're affected

  • Server takeover via code execution
  • Full system compromise as current user
  • Service disruption
  • Data theft risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS70th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.3% chance of exploitation activity in the next 30 days, which ranks it in the 70th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

10 events over 59 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. OpenVAS check added
  4. Patch availablerecord updated
  5. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 10.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for ColdFusion 2025, not every advisory.