CVE-2026-47910
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 an Incorrect Authorization 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 · moderate confidenceDreamweaver Desktop versions 21.7 and earlier contain an incorrect authorization vulnerability that allows arbitrary file system read. When a user opens a malicious file, the application fails to properly restrict file system access, enabling reading sensitive files and directories outside the intended scope. This represents a path traversal or directory traversal vulnerability combined with authorization bypass, with scope changed in CVSS terms.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Dreamweaver versionOpen Dreamweaver and go to Help > About Adobe Dreamweaver, or check the Windows Registry at HKLM\SOFTWARE\Adobe\Dreamweaver\InstallVersion, or check the version listed in Add/Remove ProgramsAffected if The displayed version is 21.7 or earlier (versions below 21.8 are affected)
-
Confirm the version is in vulnerable rangeCompare the installed version number to the affected range: any version less than 21.8 is vulnerableAffected if The installed version is less than 21.8 (for example, 21.7, 21.6, 21.5, etc.)
You are affected if Dreamweaver Desktop version 21.7 or earlier is installed, as the arbitrary file read vulnerability exists in these versions when opening files.
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 to a version beyond 21.7 once the patch is released. Until then, advise users to avoid opening files from untrusted or unverified sources, and consider implementing additional file system permission restrictions to limit potential exposure.
Dreamweaver version 21.8 or later
- 1. Open Adobe Creative Cloud desktop application or Dreamweaver
- 2. Navigate to the Updates section
- 3. Look for Dreamweaver update to version 21.8 or later
- 4. Apply the update and restart Dreamweaver if prompted
- 5. Verify the installed version by going to Help > About Adobe Dreamweaver to confirm version 21.8 or higher is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47910 — 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-47910 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