dbcve.org
ColdfusionApplication · Adobe

CVE-2026-47928

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ColdFusion versions 2023.19, 2025.8 and earlier are affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. The vulnerable component is restricted to an administrative network zone by default. Exploitation of this issue does not require user interaction. Scope is changed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ColdFusion versions 2023.19 and earlier (and 2025.8 and earlier) contain an improper input validation vulnerability that allows authenticated or network-adjacent attackers to achieve arbitrary code execution in the context of the current user. The vulnerable component is limited to administrative network zones by default, but the changed scope means the vulnerability can impact resources outside the original security boundary.

MitigationApply vendor patches for the affected ColdFusion versions immediately; ensure the administrative network zone restriction remains enforced and consider additional network segmentation as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ColdfusionApplication
Affected:= 2023= 2025

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ColdFusion version
    Access ColdFusion Administrator (typically at /cfadmin or check the version file in the installation directory). Alternatively, check the ColdFusion welcome page or use the Server Manager to view version information. Compare the version number to the affected ranges: ColdFusion 2023 versions 2023.19 and earlier, or ColdFusion 2025 versions 2025.8 and earlier.
    Affected if The installed ColdFusion version is 2023.19 or earlier for the 2023 branch, or 2025.8 or earlier for the 2025 branch.
  2. Verify ColdFusion is network-accessible
    Determine if the ColdFusion server is exposed to network requests from untrusted sources. Check firewall rules, load balancer configurations, or reverse proxy settings that expose ColdFusion ports (default 8500, 8501, or 80/443) to the internet or untrusted networks.
    Affected if ColdFusion HTTP/HTTPS endpoints are reachable from untrusted network segments or the public internet.
  3. Confirm unauthenticated endpoints are exposed
    Review ColdFusion web server configuration and ColdFusion Administrator settings to identify any publicly accessible CFM endpoints, REST services, or API gateways that do not require authentication.
    Affected if Any ColdFusion endpoints that process user-supplied input are accessible without authentication.
  4. Check for custom or third-party input-handling code
    Review the webroot for CFM files that accept URL parameters, form inputs, or HTTP headers and pass them to sensitive functions (such as evaluate(), cfexecute(), or database queries). Examine any custom REST handlers or API integrations.
    Affected if The server runs custom CFM code or third-party applications that accept and process unauthenticated user input without proper validation.

A server is affected if it runs ColdFusion 2023.19 or earlier, or 2025.8 or earlier, and has unauthenticated network-accessible endpoints that accept user input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for the affected ColdFusion versions immediately; ensure the administrative network zone restriction remains enforced and consider additional network segmentation as defense-in-depth.

Recommended fix Moderate confidence

ColdFusion 2023 Update 20+ or ColdFusion 2025 Update 9+ (versions subsequent to 2023.19 and 2025.8 respectively)

  1. 1. Identify the current ColdFusion version installed by accessing the ColdFusion Administrator or checking the version info file
  2. 2. For ColdFusion 2023 users: Upgrade to ColdFusion 2023 Update 20 or later (a version newer than the vulnerable 2023.19)
  3. 3. For ColdFusion 2025 users: Upgrade to ColdFusion 2025 Update 9 or later (a version newer than the vulnerable 2025.8)
  4. 4. Download the update from the official Adobe ColdFusion downloads page (helpx.adobe.com)
  5. 5. Back up your ColdFusion instance and application data before applying the update
  6. 6. Apply the update following Adobe's standard ColdFusion update installation procedures
  7. 7. After updating, verify the ColdFusion Administrator shows the new version number
  8. 8. Test critical application functionality to ensure the update did not break existing features
Caveat Standard ColdFusion updates typically maintain backward compatibility but always test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47928 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data