CVE-2026-48322
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedColdFusion is affected by an Improper Control of Generation of Code ('Code Injection') vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.
In the news
Third-party coverage- Firefox, Chrome, Adobe, and VMware Updates Fix Multiple Critical ...
- Adobe Patches Critical ColdFusion Vulnerabilities - SecurityWeek
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceColdFusion contains a code injection vulnerability allowing unauthenticated attackers to execute arbitrary code in the context of the current user. The vulnerability does not require user interaction and involves improper control of code generation, likely through malicious CFML or system command injection. The changed scope indicates impact extends beyond the vulnerable ColdFusion component to adjacent system resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2023= 2025CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ColdFusion versionLocate the ColdFusion installation and check the version number through the ColdFusion Administrator interface or version file in the installation directoryAffected if The installed version is Adobe ColdFusion 2023 or Adobe ColdFusion 2025
-
Verify ColdFusion service exposureDetermine if the ColdFusion service is accessible over the network by checking the listening ports (typically 8500 or 443 for Enterprise) and whether the CFIDE/administrator directory is publicly reachableAffected if The ColdFusion Administrator interface or CFML endpoints are exposed without authentication to untrusted networks
-
Inspect CFML application filesReview CFML files in the web root and subdirectories for suspicious or unexpected code, particularly usage of tags like cfexecute, cfshell, or tags that invoke system commandsAffected if Unrecognized or malicious CFML code is present that could indicate exploitation attempts or backdoors
-
Check for unauthorized process executionMonitor running processes under the ColdFusion service account for unusual or unexpected command executions that were not initiated by legitimate applicationsAffected if The ColdFusion service is executing commands or processes that were not authored by your development team
You are affected if Adobe ColdFusion 2023 or 2025 is installed and the service is accessible, as the unauthenticated code injection vulnerability can be exploited without user interaction.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided ColdFusion security patch immediately to remediate the code injection vulnerability. As an interim measure, restrict ColdFusion service account permissions and disable unnecessary ColdFusion tags/functions that could enable code execution.
- Consultation8.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48322 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data