CVE-2026-27305
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 2023.18, 2025.6 and earlier are 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.
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 2023.18 and 2025.6 and earlier contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files outside the intended directory scope by manipulating file path inputs. The vulnerability requires no user interaction and could expose sensitive configuration files, credentials, or application source code.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 ColdFusion versionAccess the ColdFusion Administrator console and navigate to the System Information or About page to view the exact version number. Alternatively, check the version file in the ColdFusion installation directory.Affected if ColdFusion 2023 version is 2023.18 or earlier, or ColdFusion 2025 version is 2025.6 or earlier
-
Confirm web service is runningVerify that the ColdFusion web service or Administrator interface is accessible over HTTP/HTTPS. The path traversal vulnerability is exploitable through web request parameters.Affected if ColdFusion web endpoints are exposed and accessible to unauthenticated users
-
Inspect web server logs for traversal patternsReview web server access logs (IIS, Apache, or ColdFusion's own logs) for URL patterns containing '../' or encoded traversal sequences in query parameters.Affected if Logs contain directory traversal attempts (e.g., ../../../') pointing to sensitive system files outside the web root
-
Verify file access outside web rootCheck if any files outside the designated web root directory have been accessed through ColdFusion endpoints, particularly configuration files, system files, or files from other applications on the same server.Affected if Evidence shows arbitrary file reads from directories outside the ColdFusion web root
Environment is affected if running ColdFusion 2023 version 2023.18 or earlier, or ColdFusion 2025 version 2025.6 or earlier, with the web interface exposed.
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 patches by upgrading ColdFusion to version 2023.18 or 2025.6 (or later), or apply any subsequent security updates released by Adobe. Restrict file system permissions and monitor for anomalous file access patterns as a defense-in-depth measure.
ColdFusion 2023.19+ or ColdFusion 2025.7+ (latest available version)
- 1. Back up your current ColdFusion installation and all applications before proceeding with the update.
- 2. Identify your current ColdFusion version by accessing the ColdFusion Administrator or checking the version information.
- 3. For ColdFusion 2023 users: Upgrade to ColdFusion 2023 version 2023.19 or later.
- 4. For ColdFusion 2025 users: Upgrade to ColdFusion 2025 version 2025.7 or later.
- 5. Download the latest ColdFusion update from the official Adobe ColdFusion download page or through your Adobe licensing portal.
- 6. Apply the update following Adobe's standard ColdFusion update installation procedure.
- 7. After updating, verify the patch was applied successfully and test critical file operation functionality.
- 8. Monitor Adobe ColdFusion security bulletins for any subsequent patches.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27305 — 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-27305 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