CVE-2026-34619
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 result in a Security feature bypass. An attacker could leverage this vulnerability to access 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 2023.18, 2025.6 and earlier contain a path traversal vulnerability allowing attackers to bypass security restrictions and access unauthorized files or directories outside the intended web root boundaries. The vulnerability is exploitable without any user interaction, making it particularly dangerous.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ColdFusion versionAccess the ColdFusion Administrator console and navigate to the System Information or Settings page to view the installed version number. Alternatively, check the version info in the ColdFusion installation directory or via command line if available.Affected if The installed version is 2023.18 or earlier, or 2025.6 or earlier.
-
Confirm ColdFusion edition and buildVerify the specific build number of ColdFusion if visible in the System Information page, as minor updates within the same major version may contain different patch levels.Affected if The build number corresponds to an unpatched release prior to the vendor fix.
-
Verify directory restriction configurationCheck if any directory restriction or file access controls are configured in ColdFusion Administrator under Security settings (RESTful Services, Access Protection, or similar).Affected if Directory restrictions are in place, as the vulnerability specifically allows bypassing these restrictions to access unauthorized files.
-
Review access logs for anomalous file access patternsExamine ColdFusion server logs and web server access logs for unusual file read requests outside expected directories, particularly looking for patterns involving directory traversal sequences (e.g., ../../).Affected if Unusual traversal-style file access attempts are observed in logs, indicating potential exploitation attempts.
A user is affected if their ColdFusion installation is version 2023.18 or earlier, or 2025.6 or earlier, and directory restrictions are configured.
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-supplied patches for ColdFusion 2023 and 2025 to address the path traversal vulnerability. Restrict file system access permissions as a defense-in-depth measure until patching is completed.
ColdFusion 2023.19+ or ColdFusion 2025.7+ (or latest available versions)
- Log in to the Adobe ColdFusion administrator console
- Navigate to the Updates section in the ColdFusion Administrator
- Check for available updates and install the latest ColdFusion update
- Alternatively, download the latest ColdFusion update from helpx.adobe.com and apply manually
- Restart the ColdFusion server after applying the update
- Verify the update was successful by checking the ColdFusion version in the Administrator
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34619 — 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-34619 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