dbcve.org
DreamweaverApplication · Adobe

CVE-2026-47909

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 21.8 or later.
See remediation →
66/100
Remediation priority · Elevated
No privileges

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 · unedited
Dreamweaver Desktop versions 21.7 and earlier are affected by an Improper Input Validation vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. 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 · high confidence

Dreamweaver Desktop versions 21.7 and earlier contain an improper input validation vulnerability that allows an attacker to read arbitrary files from the filesystem outside the intended access scope. The scope is changed, meaning the vulnerability can impact components beyond the vulnerable component itself. Exploitation requires user interaction where a victim must open a malicious file.

MitigationUpdate Dreamweaver Desktop to a version newer than 21.7 when a patch becomes available. Until then, avoid opening untrusted or suspicious files in Dreamweaver.

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
DreamweaverApplication
Affected:< 21.8

CVSS 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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Dreamweaver installation
    Check for Dreamweaver installation on the system. Common installation paths: Windows: C:\Program Files\Adobe\Adobe Dreamweaver [version] or C:\Program Files (x86)\Adobe\Adobe Dreamweaver [version]; macOS: /Applications/Adobe Dreamweaver [version]. Use registry (Windows) or filesystem scan to locate.
    Affected if Dreamweaver is found installed on the system
  2. Determine installed Dreamweaver version
    Windows: Check Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Dreamweaver\InstallVersion or right-click Dreamweaver.exe > Properties > Details tab. macOS: Right-click Dreamweaver.app > Get Info or run: defaults read /Applications/Adobe\ Dreamweaver\*/Adobe\ Dreamweaver.app/Contents/Info CFBundleShortVersionString
    Affected if Version returned is 21.7 or earlier, or any version below 21.8
  3. Confirm version comparison against CVE threshold
    Compare the discovered version number to the affected range: versions prior to 21.8 are vulnerable. Document the exact version found.
    Affected if Installed version is less than 21.8 (e.g., 21.7, 21.6, earlier)
  4. Assess exposure context
    Determine if Dreamweaver is actively used to open external files. This vulnerability is triggered when a victim opens a malicious crafted file. Check recent file open activity or user workflows.
    Affected if Users open external files in Dreamweaver and version is below 21.8

If Adobe Dreamweaver is installed with a version lower than 21.8 and users open files within the application, the environment is potentially affected by this arbitrary file system read vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 21.8 or later
Fixed in 21.8
Interim mitigation

Update Dreamweaver Desktop to a version newer than 21.7 when a patch becomes available. Until then, avoid opening untrusted or suspicious files in Dreamweaver.

Recommended fix High confidence

Dreamweaver 21.8 or later

  1. Open Dreamweaver and navigate to Help > About Adobe Dreamweaver to confirm the current version number
  2. Close Dreamweaver completely
  3. Download Dreamweaver version 21.8 or later from the official Adobe website at helpx.adobe.com
  4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. Restart Dreamweaver after installation completes
  6. Verify the installed version is 21.8 or later via Help > About Adobe Dreamweaver

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dreamweaver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47909 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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