# CVE-2023-26360: Adobe ColdFusion Deserialization of Untrusted Data

> Attackers can execute arbitrary code on Adobe ColdFusion servers due to improper access control, requiring no user interaction.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 15 Mar 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-p86r-cr5m-73hp

## What is CVE-2023-26360?

CVE-2023-26360 is a high-severity missing authorization vulnerability in Adobe Coldfusion, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Adobe ColdFusion versions 2018 Update 15 (and earlier) and 2021 Update 5 (and earlier) are affected by an Improper Access Control vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2023-26360?

It affects 1 product.


Products: Adobe Coldfusion.

## How do I fix CVE-2023-26360?

No fix has been published for CVE-2023-26360 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Apr 2023.

## Is CVE-2023-26360 being exploited?

Yes. Attackers have exploited CVE-2023-26360 in the wild since at least 15 Mar 2023.

Public exploit code:

- https://github.com/jakabakos/CVE-2023-26360-adobe-coldfusion-rce-exploit (github_poc): https://github.com/jakabakos/CVE-2023-26360-adobe-coldfusion-rce-exploit
- Exploit for Arbitrary File Read for CVE-2023-26360 - Adobe Coldfusion (github_poc): https://github.com/yosef0x01/CVE-2023-26360
-  Adobe ColdFusion CVE-2023-26360/CVE-2023-29298 自动化实现反弹 (github_poc): https://github.com/CuriousLearnerDev/ColdFusion_EXp
- Exploit for Remote Code Execution in ColdFusion 2021 (CVE-2023-26360) (github_poc): https://github.com/H3rm1tR3b0rn/CVE-2023-26360-RCE
- This exploit is based on CVE-2023-26360 (https://nvd.nist.gov/vuln/detail/CVE-2023-26360) and was built on top of the Metasploit module and the jakabakos/CVE-2023-26360-adobe-coldfusion-rce-exploit. (github_poc): https://github.com/joaoaugustom/Adobe_ColdFusion_RCE_Unauthenticated
- Adobe ColdFusion Unauthenticated Remote Code Execution (metasploit)

## Other vulnerabilities in Adobe Coldfusion

- [CVE-2026-48282](https://insights.sbomify.com/CVE-2026-48282/): Adobe ColdFusion Path Traversal (critical 10.0, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26360 and fix it if it is affected.

What it is: CVE-2023-26360 is a high-severity missing authorization vulnerability in Adobe Coldfusion, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-26360 in the wild since at least 15 Mar 2023.

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-2023-26360/ (Markdown: https://insights.sbomify.com/CVE-2023-26360/index.md)
```

## Sources

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

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