Skip to content
major vulnerability· requires attention

Widely deployed enterprise app; critical RCE via unrestricted file upload.

Web

CVE-2026-48283

10.0
Critical
EPSS 1%Patch availableJul 1, 2026

Unrestricted upload of dangerous file enables remote code execution in ColdFusion.

common questions

Is CVE-2026-48283 being exploited?

Not confirmed. CVE-2026-48283 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 1.3% probability of exploitation in the next 30 days.

How severe is CVE-2026-48283?

CVE-2026-48283 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-48283?

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

What does CVE-2026-48283 affect?

CVE-2026-48283 affects Adobe ColdFusion 2025.9, Adobe ColdFusion 2023.20, Earlier ColdFusion versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48283?

Patch now; restrict file uploads; enable validation.

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

executive summary
technical analysis
affected
Adobe ColdFusion 2025.9Adobe ColdFusion 2023.20Earlier ColdFusion versions
impact

RCE via dangerous file upload; code runs with server privileges under current user context.

action required

Immediate action required

affected versions
Adobe ColdFusion 2023
  • affected<= 20
vendor says fixed in21
Adobe ColdFusion 2025
  • affected<= 9
vendor says fixed in10

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