CVE-2026-48318 in Adobe ColdFusion
ColdFusion is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. Exploitation of this issue does not require user interaction. Scope is changed.
Quick answer
Adobe ColdFusion should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Adobe ColdFusion 2025 Update 10 and earlier
- Adobe ColdFusion 2023 Update 21 and earlier
Fixed versions
- Adobe ColdFusion 2025 Update 11 or later
- Adobe ColdFusion 2023 Update 22 or later
How to fix it
CVE-2026-48318 is a information disclosure issue in Adobe ColdFusion. Update from Adobe ColdFusion 2025 Update 10 and earlier to Adobe ColdFusion 2025 Update 11 or later or newer. Keep it simple: upgrade first, then test the normal user flow.
- Find every place where Adobe ColdFusion is installed or used.
- Upgrade Adobe ColdFusion to Adobe ColdFusion 2025 Update 11 or later or a newer fixed release from the vendor.
- If you cannot upgrade right away, limit access to the affected feature until the update is done.
- Restart or redeploy the service if the product needs it after the update.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is Adobe ColdFusion 2025 Update 11 or later or newer.
- Run a normal login, admin, and user flow to make sure the site still works.
- Check logs for new errors after the update.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-48318?
Adobe ColdFusion versions listed as affected should be reviewed: Adobe ColdFusion 2025 Update 10 and earlier, Adobe ColdFusion 2023 Update 21 and earlier.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.