CVE-2023-26359
Adobe ColdFusion Deserialization of Untrusted Data Vulnerability
Adobe ColdFusion
Adobe ColdFusion versions 2018 Update 15 (and earlier) and 2021 Update 5 (and earlier) are affected by a Deserialization of Untrusted Data vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 21 August 2023. US federal agencies were required to remediate it by 11 September 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 17%, which is higher than 97.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2023-26359 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2023-26359.
What does CVE-2023-26359 affect?
CVE-2023-26359 affects Adobe ColdFusion. Adobe ColdFusion versions 2018 Update 15 (and earlier) and 2021 Update 5 (and earlier) are affected by a Deserialization of Untrusted Data vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction.
How severe is CVE-2023-26359?
CVE-2023-26359 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 17%, higher than 97.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 11 September 2023.
How should organisations respond to CVE-2023-26359?
Apply the vendor patch for Adobe ColdFusion as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.