ColdfusionApplication · Adobe

CVE-2026-48364

HIGH · 8.2 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
5 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 Uncontrolled Search Path Element vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file. 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 Uncontrolled Search Path Element vulnerability allowing arbitrary code execution. An attacker can place a malicious file that gets loaded by ColdFusion when the victim opens it, achieving code execution in the context of the current user. The scope changed indicates the vulnerability can impact components beyond the vulnerable ColdFusion installation.

MitigationUpgrade ColdFusion to version 2025.10 or later (for 2025.x) and 2023.21 or later (for 2023.x) to resolve the uncontrolled search path vulnerability. Restrict file access permissions and validate file loading paths as a defense-in-depth measure until patching is complete.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 ColdFusion installation and version
    Check the ColdFusion version by inspecting the admin console, checking the version file, or running the cfadmin API to confirm the exact build number (such as 2025.9, 2023.20, or earlier)
    Affected if The installed version is 2025.9 or earlier, or 2023.20 or earlier (not 2025.10+/2023.21+)
  2. Review file system permissions on ColdFusion directories
    Examine write permissions on ColdFusion installation directories and subdirectories where the application loads libraries or executables
    Affected if Low-privilege users or attackers can write to directories in ColdFusion's library or binary search path
  3. Inspect for unexpected DLL or executable files
    Scan ColdFusion bin, lib, and common library directories for newly created or suspicious files that do not belong to the standard ColdFusion installation
    Affected if Unexpected DLL or executable files exist in directories that ColdFusion loads from at startup or during operation
  4. Check process environment and PATH configuration
    Review the ColdFusion service process environment variables and any custom search path configurations that define where the application loads binaries from
    Affected if The search path includes writable locations accessible to untrusted users, or contains relative/untrusted paths

A user is affected if they run a vulnerable ColdFusion 2023.x (≤2023.20) or 2025.x (≤2025.9) version AND an attacker can place a malicious file in any directory that ColdFusion searches for libraries or executables.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ColdFusion to version 2025.10 or later (for 2025.x) and 2023.21 or later (for 2023.x) to resolve the uncontrolled search path vulnerability. Restrict file access permissions and validate file loading paths as a defense-in-depth measure until patching is complete.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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