dbcve.org
ColdfusionApplication · Adobe

CVE-2026-48363

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 where the application loads resources from an attacker-controlled location. By placing a malicious file in a directory the application searches, an attacker can achieve arbitrary code execution in the context of the current user when the victim opens the malicious file.

MitigationUpgrade ColdFusion to the vendor-patched version. Until then, restrict file system permissions and avoid opening untrusted files in the ColdFusion environment.

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 installed ColdFusion version
    Check the ColdFusion version through the Administrator interface (Help > About Adobe ColdFusion) or by reviewing installation logs and registry entries for the ColdFusion installation path
    Affected if The installed version is ColdFusion 2025.9 or earlier, or ColdFusion 2023.20 or earlier (including all earlier 2023 and 2025 releases)
  2. Review ColdFusion search paths for libraries
    Examine the system PATH environment variable and any custom library paths configured in the ColdFusion Administrator under Server Settings > Java/JVM or in the jvm.config file
    Affected if The search path includes directories writable by untrusted users or network locations accessible to attackers
  3. Inspect directory permissions on ColdFusion search paths
    For each directory in the ColdFusion search path (especially bin, lib, and custom paths), check file system permissions using OS-native commands (icacls on Windows, ls -la on Linux) to determine if non-privileged users can write files
    Affected if Any directory in the ColdFusion search path allows write access to untrusted users, enabling placement of malicious files
  4. Scan for unexpected files in ColdFusion search directories
    List all files in the identified search path directories (particularly bin and lib folders within the ColdFusion installation) and compare against expected baseline files
    Affected if Unexpected DLL, JAR, or resource files exist in ColdFusion search directories that were not part of the original installation

You are affected if running ColdFusion 2023 versions 2023.20 or earlier, or ColdFusion 2025 versions 2025.9 or earlier, AND your search path directories are writable by untrusted users or contain unexpected files.

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

Upgrade ColdFusion to the vendor-patched version. Until then, restrict file system permissions and avoid opening untrusted files in the ColdFusion environment.

Recommended fix Moderate confidence

ColdFusion 2023 Update 21+ or ColdFusion 2025 Update 10+ (depending on your baseline version)

  1. 1. Identify your current ColdFusion version by checking the ColdFusion Administrator console or the version info in the installation directory.
  2. 2. Navigate to the Adobe ColdFusion security bulletins page (helpx.adobe.com) to obtain the latest security updates.
  3. 3. Download and install ColdFusion 2023 Update 21 or later for the 2023 version.
  4. 4. Download and install ColdFusion 2025 Update 10 or later for the 2025 version.
  5. 5. After applying the update, restart the ColdFusion application server service.
  6. 6. Verify the installation was successful by checking the ColdFusion Administrator > System Information page shows the updated version number.
Caveat Standard ColdFusion update apply procedure - test in staging environment before production deployment; ensure your custom code and third-party integrations are compatible with the latest update

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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