PatchSiren cyber security CVE debrief
CVE-2026-34633 Adobe CVE debrief
A Server-Side Request Forgery (SSRF) vulnerability in Adobe ColdFusion could allow a low-privileged attacker to gain elevated access to internal resources. This CVE was published on 2026-10-13T20:21:44.259Z and was last modified on 2026-10-14T14:43:00.627Z. The vulnerability affects ColdFusion 2025 versions up to 2025.0.13 and ColdFusion 2023 versions up to 2023.0.25. Exploitation of this issue does not require user interaction. Defenders should assess exposure and prioritize patching or mitigating the vulnerability.
- Vendor
- Adobe
- Product
- ColdFusion 2025
- CVSS
- HIGH 7.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-13
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-13
- Advisory updated
- 2026-10-14
Who should care
Defenders responsible for ColdFusion systems, particularly those with versions up to 2025.0.13 or 2023.0.25, should assess exposure and prioritize patching or mitigating the vulnerability. This includes operators, platform administrators, vulnerability management teams, and security teams who manage or secure ColdFusion deployments.
Why it matters
The SSRF vulnerability in Adobe ColdFusion could allow a low-privileged attacker to gain elevated access to internal resources, posing a risk to systems with affected versions.
- Potential privilege escalation
- Increased risk of internal resource compromise
Technical summary
The CVE record describes a Server-Side Request Forgery (SSRF) vulnerability in Adobe ColdFusion, which could result in privilege escalation. A low-privileged attacker could exploit this vulnerability to gain elevated access to internal resources. The vulnerability affects ColdFusion 2025 versions up to 2025.0.13 and ColdFusion 2023 versions up to 2023.0.25. Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems with ColdFusion 2025 versions up to 2025.0.13 and ColdFusion 2023 versions up to 2023.0.25.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems with ColdFusion 2025 versions up to 2025.0.13 and ColdFusion 2023 versions up to 2023.0.25.
Recommended defensive actions
- Verify ColdFusion version and apply patches if necessary
- Restrict access to ColdFusion systems
- Monitor for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source item provide details on the SSRF vulnerability in Adobe ColdFusion, including affected versions and potential impacts. However, additional information on exploitation or specific attacks is limited.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-34633 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-34633
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-34633 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-34633
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
ColdFusion | Server-Side Request Forgery (SSRF) (CWE-918)
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/34xxx/CVE-2026-34633.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://www.adobe.com/trust/security/products/coldfusion/apsb26-144.html
Supplemental source - vendor-advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.