CVE-2021-26025
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 · uneditedPlugIns\IDE_ACDStd.apl in ACDSee Professional 2021 14.0 1721 has a User Mode Write Access Violation starting at IDE_ACDStd!zlibVersion+0x0000000000004e5e via a crafted BMP image.
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 confidenceThe IDE_ACDStd.apl plugin in ACDSee Professional 2021 14.0 1721 contains a memory corruption vulnerability triggered by parsing a crafted BMP image file, resulting in a User Mode Write Access Violation at the zlibVersion+0x4e5e offset. This indicates a buffer overflow or out-of-bounds write during BMP image parsing.
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= 14.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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 ACDSee Professional 2021 is installedCheck installed programs in Windows Control Panel or use 'Get-ItemProperty' in PowerShell for 64-bit: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*ACDSee*'}Affected if ACDSee Professional 2021 appears in the installed programs list
-
Confirm the exact version is 14.0In ACDSee, go to Help > About or right-click the executable and view Properties > Details to find the version numberAffected if Version displays as 14.0 (specifically build 1721)
-
Verify IDE_ACDStd.apl plugin existsSearch for IDE_ACDStd.apl in the ACDSee program directory, typically under C:\Program Files\ACD Systems\ACDSee\2021\ or C:\Program Files (x86)\ACD Systems\ACDSee\2021\Affected if The file IDE_ACDStd.apl is present in the plugin folder
-
Confirm BMP file handling is enabledOpen ACDSee, go to Tools > File Management Plugins or check the plugin manager to verify BMP support is loadedAffected if BMP image format support is enabled and the IDE_ACDStd.apl plugin is active
You are affected if ACDSee Professional 2021 version 14.0 build 1721 is installed with the IDE_ACDStd.apl plugin present and BMP file handling enabled.
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 dataAvoid opening untrusted or unknown BMP images in ACDSee Professional 2021 until the vendor releases a security patch. Consider using alternative image viewing applications for files from untrusted sources.
- Consultation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26025 — 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-2021-26025 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