CVE-2026-47906
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 · uneditedDreamweaver Desktop versions 21.7 and earlier are affected by a Dependency on Vulnerable Third-Party Component vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Scope is changed.
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 confidenceDreamweaver Desktop versions 21.7 and earlier depend on a vulnerable third-party component that could allow arbitrary code execution when a user opens a malicious file. The scope is changed, indicating the vulnerability impacts components beyond the third-party library itself.
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< 21.8CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Verify Dreamweaver Desktop is installedCheck your system for Adobe Dreamweaver installation. On Windows, look in Program Files/Adobe or check Programs and Features. On macOS, check /Applications for Dreamweaver.app.Affected if Dreamweaver Desktop is present on the system
-
Determine installed Dreamweaver versionOpen Dreamweaver and go to Help > About Adobe Dreamweaver, or right-click the Dreamweaver executable and select Properties > Details to view the version number.Affected if Version displayed is 21.7 or any version lower than 21.8
-
Assess file opening behaviorDetermine whether you open files from untrusted or unknown sources in Dreamweaver, as the vulnerability is exploited through opening a malicious file.Affected if You routinely open files from untrusted or unknown sources in Dreamweaver
If Dreamweaver Desktop is installed and the version is 21.7 or earlier, the environment is affected by this vulnerability.
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.
dbcve · scoped21.8
Update Dreamweaver Desktop to a version newer than 21.7 once Adobe releases a patch. Until then, avoid opening untrusted or unexpected files in Dreamweaver.
21.8
- Open Adobe Creative Cloud desktop application or navigate to the Adobe Dreamweaver download page at helpx.adobe.com
- Locate Adobe Dreamweaver in your installed applications
- Check the current version (Help > About Dreamweaver) to confirm it is below 21.8
- Initiate the update through Adobe Creative Cloud or download Dreamweaver version 21.8 directly from Adobe
- Install the update and restart Dreamweaver
- Verify the installed version is 21.8 or later by checking Help > About Dreamweaver
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47906 — 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-47906 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