Threats / Adobe / CVE-2023-26360
CVE-2023-26360
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Adobe ColdFusion vulnerability
Adobe ColdFusion contains a deserialization of untrusted data vulnerability enabling remote code execution. The flaw has been exploited in the wild.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit unsafe deserialization in ColdFusion to execute arbitrary code on affected systems. Active exploitation in the wild and high EPSS score indicate immediate risk to unpatched deployments.
CISA KEV Yes · 2023-03-155EPSS 0.97339 (verify live)6Exploit Weaponized · public PoC7CVSS 8.63CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
25 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-03-15).
Probability (EPSS)
EPSS 0.97339 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) · Affected: Adobe, ColdFusion. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-284 Improper Access Control — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious serialized object and send it to the vulnerable ColdFusion endpoint.
Business
The organization's ColdFusion server processes untrusted input without validation, creating an entry point for code execution.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger deserialization of my payload, causing arbitrary code to execute in the application context.
Business
Attackers gain the ability to run commands with the privileges of the ColdFusion process, potentially compromising the entire application.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence and move laterally through the network to access sensitive data or critical systems.
Business
The breach expands beyond the initial server, threatening data confidentiality, system integrity, and business continuity.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05