# CVE-2026-48282: Adobe ColdFusion Path Traversal

> An attacker can exploit a path traversal vulnerability in Adobe ColdFusion to achieve arbitrary code execution without user interaction.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 7 Jul 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-jfrp-7pp5-772c

## What is CVE-2026-48282?

CVE-2026-48282 is a critical path traversal vulnerability in Adobe Coldfusion, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 code execution in the context of the current user. Exploitation of this issue does not require user interaction. Scope is changed.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-48282?

It affects 1 product.


Products: Adobe Coldfusion.

## How do I fix CVE-2026-48282?

No fix has been published for CVE-2026-48282 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Jul 2026.

## Is CVE-2026-48282 being exploited?

Yes. Attackers have exploited CVE-2026-48282 in the wild since at least 7 Jul 2026.

Public exploit code:

- https://github.com/imbas007/CVE-2026-48282 (github_poc): https://github.com/imbas007/CVE-2026-48282
- Laboratory validation of CVE-2026-48282 in Adobe ColdFusion RDS, covering arbitrary CFM file write, code execution as the ColdFusion service user, auditd and PCAP evidence, event timeline reconstruction, and SOC detection recommendations. Includes Polish and English reports. (github_poc): https://github.com/g0thamRabb1t/CVE-2026-48282-coldfusion-rds-detection
- https://github.com/arpit-bansal15/cve-2026-48282-pentest-lab (github_poc): https://github.com/arpit-bansal15/cve-2026-48282-pentest-lab
- Adobe ColdFusion - RDS Arbitrary File Write (nuclei): http/cves/2026/CVE-2026-48282.yaml

## Other vulnerabilities in Adobe Coldfusion

- [CVE-2023-38203](https://insights.sbomify.com/CVE-2023-38203/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2023-29300](https://insights.sbomify.com/CVE-2023-29300/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2023-26359](https://insights.sbomify.com/CVE-2023-26359/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2018-15961](https://insights.sbomify.com/CVE-2018-15961/): Adobe ColdFusion Unrestricted File Upload (critical 9.8, exploited in the wild)
- [CVE-2018-4939](https://insights.sbomify.com/CVE-2018-4939/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48282 and fix it if it is affected.

What it is: CVE-2026-48282 is a critical path traversal vulnerability in Adobe Coldfusion, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-48282 in the wild since at least 7 Jul 2026.

Affected product: Adobe Coldfusion. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48282/ (Markdown: https://insights.sbomify.com/CVE-2026-48282/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48282
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48282
- OSV: https://osv.dev/vulnerability/CVE-2026-48282

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48282/
Summaries are generated and may contain mistakes; the official description above is the record.