CVE-2026-48314
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 · uneditedColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to gain limited read and write access to unauthorized files or directories outside the intended restrictions. Exploitation of this issue does not require user interaction.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceColdFusion versions 2025.9, 2023.20 and earlier contain a path traversal vulnerability that allows attackers to bypass security restrictions and gain limited read/write access to files and directories outside the intended restricted path. The vulnerability is exploitable without user interaction.
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= 2023= 2025CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ColdFusion versionAccess the ColdFusion Administrator console and navigate to the 'Server Settings' > 'About' page, or check the version file in the ColdFusion installation directory (typically /cfusion/lib/boot.properties or /cfusion/CFIDE/adminapi/version.cfm)Affected if The installed version is ColdFusion 2023 version 20 or earlier, OR ColdFusion 2025 version 9 or earlier
-
Verify ColdFusion file operation components are in useReview the application's codebase and server configuration for use of ColdFusion file handling tags and functions such as <cffile>, <cfdirectory>, fileRead(), fileWrite(), or any custom file upload/download endpointsAffected if The ColdFusion server processes file operations using the affected components and no input validation hardening has been applied to restrict path references
-
Check for path traversal vulnerable endpointsAudit web application endpoints that accept file path parameters (e.g., download, read, write, or file inclusion operations) by reviewing the CFML code in the web root and /CFIDE directories for unvalidated path variables passed to file system operationsAffected if Application endpoints accept path parameters without proper validation using functions like getCanonicalPath() or path allowlisting to prevent traversal sequences like '../'
-
Inspect web server configuration for restricted path settingsReview the ColdFusion Administrator 'Security' > 'File Restrictions' settings and the underlying web server (IIS/Apache) configuration to determine which directories are configured as allowed file access boundariesAffected if The file restriction configuration allows access beyond the intended restricted directories or contains no explicit path boundaries for sensitive file operations
A system is affected if it runs ColdFusion 2023 up to version 20 or ColdFusion 2025 up to version 9 and exposes file operation functionality without strict path traversal protections.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch or upgrade to a fixed ColdFusion version. Review and audit file access controls and input validation mechanisms for path traversal vulnerabilities.
ColdFusion 2023 Update 21+ or ColdFusion 2025 Update 10+
- Check current ColdFusion version by accessing the ColdFusion Administrator console
- Back up the ColdFusion installation, including the instance configuration and any custom code
- Download the latest ColdFusion update from Adobe's official download page (helpx.adobe.com) - specifically Update 21 for ColdFusion 2023 or Update 10 for ColdFusion 2025
- Stop the ColdFusion application server service
- Run the ColdFusion update installer for your respective version
- Follow the on-screen installation prompts to apply the update
- Restart the ColdFusion application server service
- Verify the update was successful by checking the version in ColdFusion Administrator
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48314 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48314 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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