dbcve.org
ColdfusionApplication · Adobe

CVE-2026-48313

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 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 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read and limited write access. 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.

In the news

Third-party coverage
Trending covered by 3 outlets this week · latest 1mo ago

Surfaced 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 confidence

ColdFusion versions 2025.9, 2023.20 and earlier contain a path traversal vulnerability allowing unauthenticated attackers to read arbitrary files outside the intended directory and achieve limited write access. The vulnerability requires no user interaction to exploit and has a changed scope, indicating impact beyond the vulnerable component's authorization boundaries.

MitigationApply the vendor-provided patch for ColdFusion 2025.9 and 2023.20 (or later patched versions). If no patch is immediately available, restrict file access permissions, implement strict input validation on file path parameters, and consider network-level segmentation to limit exposure.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ColdFusion version
    Check the ColdFusion administrator interface (typically at /cfide/administrator/) or examine the version file in the ColdFusion installation directory. The version is also visible in the ColdFusion administrator home page.
    Affected if The installed version is 2023 (any build) or 2025 (any build), specifically versions 2023.20 and earlier, or 2025.9 and earlier.
  2. Verify file operation endpoints are accessible
    Confirm that ColdFusion file handling endpoints (such as CFFILE, CFFTP, or associated file browser/admin features) are exposed and accessible over the network without requiring authentication.
    Affected if File operation features are reachable without authentication, making the path traversal exploit accessible to unauthenticated attackers.
  3. Check for input validation on file path parameters
    Review ColdFusion application configurations and any custom file handling code for proper input validation that restricts file paths to intended directories.
    Affected if No strict input validation exists on file path parameters, or path traversal sequences (..) are not properly sanitized before file operations.
  4. Assess network exposure of ColdFusion services
    Determine whether ColdFusion administrator interfaces and file-related endpoints are exposed to untrusted networks or the internet.
    Affected if ColdFusion services are accessible from untrusted networks, enabling unauthenticated attackers to reach the vulnerable component.

You are affected if your ColdFusion installation is version 2023 (any build) or 2025 (any build) and the file operation functionality is accessible to unauthenticated users without proper path traversal safeguards.

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

Apply the vendor-provided patch for ColdFusion 2025.9 and 2023.20 (or later patched versions). If no patch is immediately available, restrict file access permissions, implement strict input validation on file path parameters, and consider network-level segmentation to limit exposure.

Recommended fix High confidence

ColdFusion 2023 update 21 or later; ColdFusion 2025 update 10 or later

  1. Verify current ColdFusion version by accessing the ColdFusion Administrator or checking the version info in the installation
  2. Download the latest ColdFusion 2023 update (update 21 or later) from helpx.adobe.com
  3. Download the latest ColdFusion 2025 update (update 10 or later) from helpx.adobe.com
  4. Stop the ColdFusion application server service before applying the update
  5. Apply the appropriate update for your installed version using the Adobe update installer
  6. Restart the ColdFusion application server service after the update completes
  7. Verify the update was successful by checking the ColdFusion Administrator version info
  8. Test critical application functionality to ensure normal operation
Caveat Adobe ColdFusion updates are typically backward compatible; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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