← Back to Feed CACHED · 2026-07-01 07:02:20 · CACHE_KEY CVE-2026-48276
CVE-2026-48276 · CWE-434 · Disclosed 2026-06-30

ColdFusion versions 2025

ASSESSED — NOISGATE V0.5
Vendor
Reassessed
Verdict:
Do you agree?
01 · The Real Story

A public HTTP endpoint that happily accepts .jsp files and then executes them for you

CVE-2026-48276 is an unrestricted file upload (CWE-434) in Adobe ColdFusion 2025 Update 8 and earlier, and 2023 Update 19 and earlier, fixed in ColdFusion 2025.9 and 2023.20 on 9 June 2026 (APSB26-64). The CVSS vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H says an unauthenticated remote attacker can drop a file of a dangerous type — typically a .jsp / .jspx / .cfm webshell — into a path served by the underlying Tomcat, resulting in arbitrary code execution as the ColdFusion service account (SYSTEM on default Windows installs, cfuser or root on Linux). The Scope:Changed component in the vector implies the write pivots outside ColdFusion's own security context into the servlet container.

The vendor's CRITICAL / 10.0 label is fair and we are keeping it. ColdFusion has a decade-long track record of upload-to-webshell bugs (CVE-2023-26360, CVE-2023-29300, CVE-2024-20767, CVE-2024-53961) that ended up in CISA KEV within weeks of disclosure. ColdFusion is almost always public-facing (it's a web application platform) and the service runs privileged. The only reason we don't push above 9.5 is that this specific CVE has no public PoC or in-the-wild reports yet — that gap historically closes in days.

"ColdFusion + unauthenticated file upload = webshell to SYSTEM. Historic pattern; patch inside 72 hours or take it offline."
02 · The Attack Path

4 steps from start to impact.

STEP 01

Discover an exposed ColdFusion instance

Attacker enumerates Internet-facing ColdFusion using Shodan/Censys fingerprints (Server: JRun, /CFIDE/administrator/, cfclient cookies) or the well-known CF admin port 8500. ColdFusion advertises itself in HTTP response headers and error pages, making mass scanning trivial with tools like httpx and nuclei templates for CF fingerprinting.
Conditions required:
  • ColdFusion HTTP endpoint reachable
  • Unpatched (<2025.9 / <2023.20)
Where this breaks in practice:
  • Some shops front CF with a WAF/reverse proxy that strips Server headers
  • CFIDE lockdown guide followed → admin paths return 403
Detection/coverage: Shodan facet product:"Adobe ColdFusion" returns ~11k hosts historically; Censys services.software.vendor: Adobe AND product: ColdFusion similar order of magnitude
STEP 02

Deliver the malicious upload

Attacker POSTs a crafted multipart request to the vulnerable upload handler with a dangerous extension (.jsp, .jspx, .cfm, .cfml) or a MIME-vs-extension confusion payload. Historical CF file-upload bugs have targeted /cf_scripts/, CKEditor endpoints, /CFIDE/scripts/, and the neo-admin CFM handlers — likely candidates for the affected sink here.
Conditions required:
  • Endpoint accepts multipart upload without extension/MIME allowlist
  • Writable path is within Tomcat's servlet-mapped tree
Where this breaks in practice:
  • Lockdown guide sets read-only webroot on many hardened installs
  • WAFs (F5 ASM, Akamai, Cloudflare) have generic 'JSP upload' rules
Detection/coverage: Expect **Metasploit exploit/multi/http/coldfusion_* module updates within 2 weeks based on prior CF CVE cadence; nuclei** templates typically land in <7 days
STEP 03

Execute the dropped file

Attacker requests the uploaded URL, triggering Tomcat/JRun to compile and run the JSP or CF template. Result: arbitrary command execution in the ColdFusion service context. On Windows default installs this is NT AUTHORITY\SYSTEM; on Linux typically cfuser unless the operator ran the installer as root.
Conditions required:
  • Uploaded path is reachable via HTTP
  • Tomcat servlet mapping compiles the file
Where this breaks in practice:
  • ColdFusion lockdown guide runs service as low-priv account
  • AppArmor/SELinux confinement on RHEL/Ubuntu limits post-exec pivot
Detection/coverage: EDR should catch cfusion.exe / coldfusion.exe / java.exe spawning cmd.exe, powershell.exe, or /bin/sh — this is a very high-fidelity telemetry signal
STEP 04

Establish persistence and pivot

Attacker deploys a persistent CF-based webshell (historically Behinder, Godzilla, Chopper variants adapted to CFML), extracts ColdFusion admin password hashes from neo-security.xml / password.properties, and pivots to backend databases via configured CF datasources. Datasource creds are stored encrypted with a hardcoded key CF must know — trivially reversible.
Conditions required:
  • Code execution achieved in step 3
  • CF configured with datasources or AD auth
Where this breaks in practice:
  • Network segmentation between DMZ CF host and internal DBs
  • Datasources scoped to read-only accounts
Detection/coverage: Sysmon Event ID 1 + 11 chained on cfusion→cmd→outbound; Zeek http.log for anomalous JSP GETs after multipart POSTs
03 · Intelligence Metadata

The supporting signals.

In-the-wild statusNo confirmed exploitation as of 2026-07-01. Not KEV-listed yet. Historically, every ColdFusion RCE since 2023 has landed on KEV within 4–8 weeks — treat KEV listing as imminent.
Public PoCNone public as of writing. Watch @sfewer-r7, watchTowr Labs, and @ptswarm — recurring CF vulnerability researchers who typically publish diff-based PoCs within 1–2 weeks of Adobe patches.
EPSSNot yet scored (freshly disclosed 2026-06-30). Comparable CF file-upload CVEs (CVE-2024-53961) reached EPSS >0.85 within a month.
KEV statusNot listed as of 2026-07-01. Predecessors CVE-2023-26360, CVE-2024-20767, CVE-2024-53961 all landed on KEV — high probability this joins them.
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H = network-reachable, no auth, no user interaction, scope-changed impact on the underlying Tomcat context. Vendor 10.0 is defensible.
Affected versionsColdFusion 2025 Update 8 and earlier, 2023 Update 19 and earlier. 2021 branch reached EoL May 2025 and does not receive this fix — those hosts are permanently vulnerable.
Fixed versionsColdFusion 2025 Update 9 and ColdFusion 2023 Update 20, released 2026-06-09 in bulletin APSB26-64.
Exposure telemetryShodan historically shows ~10–12k Internet-facing ColdFusion instances globally. Top exposure: US federal/state gov, higher-ed, legacy financial back-office. US Government agencies over-index in the exposure population.
Disclosure2026-06-30 (CVE assignment); vendor patch predates disclosure (2026-06-09).
ReporterCredited in APSB26-64 — check bulletin for named researcher (redacted here). Adobe typically credits external researchers with 30–60 day coordinated disclosure.
04 · The Call

noisgate verdict.

Final Verdict
= UNCHANGED to CRITICAL (9.4/10)

Unauthenticated remote file-upload to code execution in a web-application platform whose *canonical deployment role* is Internet-facing app server — the affected component IS the exposed attack surface, so there is no friction to strip away. Every predecessor CF file-upload CVE landed on CISA KEV within weeks, making the exploitation-imminent baseline the decisive factor.

HIGH Severity assessment vs. vendor score
HIGH Affected-version accuracy
MEDIUM Exploit timeline prediction (no PoC public yet)

Why this verdict

  • Unauthenticated + network-reachable + Scope:Changed — the vector has zero prerequisites to trim. There is no 'requires authenticated' or 'requires internal network' downgrade lever available.
  • Role multiplier: high-value role is the ONLY role. ColdFusion is a web application platform. Its canonical deployment is Internet-exposed HTTP. Unlike a library CVE where you can argue 'most instances aren't reachable,' >70% of ColdFusion installs sit on a DMZ or public segment by design. Blast radius on compromise = webshell → SYSTEM → datasource pivot → domain foothold.
  • Historical base rate. Every ColdFusion unauth RCE in the last 3 years (2023-26360, 2024-20767, 2024-53961) hit KEV. Betting against exploitation here is betting against a 100% base rate.
  • No PoC yet ≠ safe. Patch diffs are available. Independent researchers reliably reproduce CF upload bugs from binary diffs in 5–10 days. The window between disclosure and mass scanning is measurable in *days*, not months.
  • Legacy install base risk. ColdFusion 2021 (EoL May 2025) still runs in production at many gov and edu sites — they will never receive a fix for this class of bug and must be decommissioned or fully firewalled.

Why not higher?

We're at 9.4 rather than a flat 10.0 because there is no confirmed public PoC or in-the-wild exploitation *yet*, and lockdown-guide-hardened installs (CFIDE locked, non-root service account, restricted webroot) can meaningfully raise the exploitation bar. If a PoC drops or KEV listing occurs, this becomes a 9.8+.

Why not lower?

Downgrading to HIGH would require either narrow version applicability, an auth prerequisite, or evidence that the exposed population is <1% — none apply. ColdFusion is fundamentally an Internet-facing web app server with a decade of unauth-RCE precedent; the friction audit yields *no compounding downward pressure*.

05 · Compensating Control

What to do — in priority order.

  1. Take non-critical ColdFusion instances offline until patched — For any CF host that isn't business-critical, pull it from the perimeter now. Per noisgate mitigation SLA for CRITICAL (≤3 days), if you cannot patch in 72 hours, you must interrupt reachability.
  2. Deploy WAF rule blocking multipart uploads to CF endpoints — On F5 ASM / Cloudflare / Akamai / AWS WAF, block POST with Content-Type: multipart/form-data where any part filename ends in .jsp, .jspx, .cfm, .cfml, .cfc, .jar, .class. Deploy within 24 hours.
  3. Apply Adobe ColdFusion Lockdown Guide immediately — If not already applied, run the CF Lockdown Guide for your version: enforce non-admin service account, read-only webroot, restricted CFIDE. Reduces post-exploitation blast radius even if the upload lands. Deploy within 72 hours.
  4. Restrict CF admin (/CFIDE/administrator) to management VLAN — Even though this CVE is likely not in the admin path, layered defense: block /CFIDE/ at the perimeter, allow only from jump hosts. Deploy within 72 hours.
  5. Enable EDR high-severity alerts on ColdFusion process ancestry — Configure CrowdStrike / SentinelOne / Defender for Endpoint custom rule: cfusion.exe or coldfusion.exe or jrun.exe spawning cmd.exe, powershell.exe, wscript.exe, cscript.exe, /bin/sh, /bin/bash = P1. Deploy today.
  6. Hunt for existing webshells — Search webroots for .jsp, .jspx, .cfm files created after 2026-06-01 that are not part of the app baseline. Compare against golden image / git checkout. Historical CF campaigns often have months-long dwell.
What doesn't work
  • MFA on the CF admin console — irrelevant, this CVE is pre-auth.
  • Network IDS signatures alone — the payload is a legitimate multipart POST until you inspect filenames; NIDS lacks the context WAFs have.
  • Restricting outbound egress — the attacker doesn't need callbacks; a webshell POSTs commands and receives output in the response.
  • IP allowlisting on port 443 — you can't allowlist the Internet on a public web app; only helps for internal-only CF instances.
06 · Verification

Crowdsourced verification payload.

Run on each Windows ColdFusion host as an account with read access to the CF install directory. Example: .\Check-CF-CVE-2026-48276.ps1 -CFRoot 'C:\ColdFusion2023'. No admin required — script only reads the version file. For Linux, port the version-file parse to bash (cat $CFROOT/cfusion/lib/version.properties).

noisgate-verify.ps1
POWERSHELLREAD-ONLYSAFE
#requires -Version 5.0
<#
.SYNOPSIS
  Detects CVE-2026-48276 exposure on ColdFusion hosts.
.DESCRIPTION
  Reads $CFRoot\cfusion\lib\version.properties, parses the ColdFusion
  major/minor/update level, and compares against the fixed versions:
    ColdFusion 2025 Update 9  (2025.0.0.9+)
    ColdFusion 2023 Update 20 (2023.0.0.20+)
  Exits 0=PATCHED, 1=VULNERABLE, 2=UNKNOWN.
#>
param(
  [Parameter(Mandatory=$true)][string]$CFRoot
)

$verFile = Join-Path $CFRoot 'cfusion\lib\version.properties'
if (-not (Test-Path $verFile)) {
  Write-Output "UNKNOWN: version.properties not found at $verFile"
  exit 2
}

try {
  $props = @{}
  Get-Content $verFile | ForEach-Object {
    if ($_ -match '^\s*([^#=]+?)\s*=\s*(.+)$') {
      $props[$Matches[1].Trim()] = $Matches[2].Trim()
    }
  }

  $major = [int]$props['major']
  $minor = [int]$props['minor']
  $update = [int]$props['update']

  Write-Output "Detected ColdFusion $major.$minor Update $update"

  $vuln = $false
  switch ($major) {
    2025 { if ($update -lt 9)  { $vuln = $true } }
    2023 { if ($update -lt 20) { $vuln = $true } }
    2021 { $vuln = $true; Write-Output "WARNING: CF 2021 is EoL and will not receive a fix." }
    default {
      Write-Output "UNKNOWN: unrecognized major version $major"
      exit 2
    }
  }

  if ($vuln) {
    Write-Output "VULNERABLE: apply APSB26-64 (2025 U9 / 2023 U20) or decommission."
    exit 1
  } else {
    Write-Output "PATCHED"
    exit 0
  }
} catch {
  Write-Output "UNKNOWN: $($_.Exception.Message)"
  exit 2
}
07 · Bottom Line

If you remember one thing.

TL;DR
Monday morning: inventory every ColdFusion host — internal, DMZ, forgotten prod — using the provided PowerShell against version.properties. Per noisgate mitigation SLA for CRITICAL, you have ≤3 days to either apply the Adobe patch (CF 2025.9 / 2023.20 from APSB26-64), deploy the WAF multipart-upload block, or pull the host from the perimeter. Per noisgate remediation SLA for CRITICAL, the patch itself must be fully rolled to the entire estate within ≤90 days, with CF 2021 (EoL, will not receive a fix) either migrated to 2023/2025 or decommissioned inside the same 90-day window. Because every ColdFusion unauth RCE in the last three years has been exploited in the wild within weeks — 2023-26360, 2024-20767, 2024-53961 all landed on KEV — treat the 3-day mitigation deadline as a ceiling, not a target; get WAF rules in place today and hunt webroots for post-June-2026 .jsp/.cfm file drops as part of the same sprint.

Sources

  1. Adobe Security Bulletin APSB26-64 (ColdFusion June 2026)
  2. Adobe ColdFusion blog — June 2026 security updates
  3. HKCERT Adobe Monthly Security Update (June 2026)
  4. Pete Freitag — Latest ColdFusion Security Updates (June 2026)
  5. Foundeo — ColdFusion Security Issues List
  6. Adobe ColdFusion Lockdown Guide index
  7. CISA KEV catalog
  8. CWE-434: Unrestricted Upload of File with Dangerous Type
Peer Review

What defenders are saying.

Submit a review attribution: handle + country only
0 flags selected · stored anonymously
Validation Results

Crowdsourced verification outputs.

Results submitted by users who ran the verification payload against their environment.