dbcve.org
ColdfusionApplication · Adobe

CVE-2026-48316

CRITICAL · 10.0 CVSS v3.1 Published 2026-07-06
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
Remotely reachable No privileges Zero-click 7 weeks old

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 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.

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 2025.9, 2023.20 and earlier contain an improper input validation vulnerability that allows unauthenticated attackers to execute arbitrary code in the context of the current user without any user interaction.

MitigationApply vendor patches immediately to upgrade to patched ColdFusion versions; if unavailable, implement strict input validation and consider network segmentation to limit exposure.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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 ColdFusion installation version
    Access the ColdFusion Administrator interface and navigate to the 'Server Settings' > 'Settings' page, or check the version file in the ColdFusion installation directory (typically cf_root/lib/../version.properties or via the 'cfapplication' mApplication version output)
    Affected if Installed version is ColdFusion 2023.20 or earlier, OR ColdFusion 2025.9 or earlier
  2. Confirm ColdFusion edition and build
    In ColdFusion Administrator, check the 'About Adobe ColdFusion' page which displays the exact version number, build number, and edition
    Affected if Build number corresponds to versions earlier than the patched releases for 2023.20 or 2025.9
  3. Verify network exposure of ColdFusion services
    Check firewall rules and network configuration to determine if ColdFusion HTTP ports (default 8500, 8501, or custom ports) are accessible from unauthenticated external networks
    Affected if ColdFusion web interfaces are exposed to the internet or untrusted networks without authentication requirements
  4. Review access control on ColdFusion Administrator
    Examine the administrator web application's authentication configuration and ensure all admin paths require valid credentials
    Affected if Administrator interface or any CFML endpoint accepts requests without requiring authentication

User is affected if running ColdFusion 2023.20 or earlier, or ColdFusion 2025.9 or earlier, with the ColdFusion services exposed to unauthenticated network access.

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 immediately to upgrade to patched ColdFusion versions; if unavailable, implement strict input validation and consider network segmentation to limit exposure.

Recommended fix Moderate confidence

Upgrade to the latest stable ColdFusion 2023 release (beyond 2023.20) and ColdFusion 2025 release (beyond 2025.9) as specified in the Adobe security bulletin

  1. Identify your current ColdFusion version by checking the ColdFusion Administrator or the version information file
  2. Back up your ColdFusion installation, including the lib directory, custom tags, and any database configurations
  3. Consult the official Adobe ColdFusion security bulletin at helpx.adobe.com for the specific patch or hotfix corresponding to your version
  4. Apply the patch following Adobe's documented installation procedure, which typically involves stopping the ColdFusion service, replacing affected files, and restarting the service
  5. After patching, verify the installation by checking the ColdFusion Administrator and testing critical applications
Caveat Review Adobe's release notes for any breaking changes or configuration requirements between your current version and the target version before upgrading

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

Fix this in Coldfusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48316 — 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-48316 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