CVE-2026-30041
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 · uneditedAn integer overflow in the PSD parser compnent of FastStone Image Viewer v8.3 allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via supplying a crafted PSD file.
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 confidenceAn integer overflow vulnerability exists in the PSD file parser of FastStone Image Viewer v8.3. When processing a specially crafted PSD file, the parser performs size calculations or memory allocation operations that can overflow due to insufficient integer bounds checking, potentially leading to heap corruption, arbitrary code execution, or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Find FastStone Image Viewer installationCheck the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'FastStone Image Viewer' or inspect typical installation directories like C:\Program Files\FastStone Image ViewerAffected if The software is not installed, the user is not affected by this specific CVE in FastStone Image Viewer
-
Determine installed versionOpen the application and go to Help > About, or check the registry value DisplayVersion in the uninstall entry found aboveAffected if The version is 8.3 exactly, indicating the affected version listed in the CVE
-
Check for PSD file handling capabilityAttempt to open or preview a PSD file in FastStone Image Viewer, or verify that .psd file association is registered to the applicationAffected if PSD files can be opened or previewed, meaning the vulnerable parser code path is reachable
-
Identify source of PSD filesReview whether the user opens PSD files from untrusted or unknown sources, or check browser/download folders for unexpected PSD filesAffected if The user processes PSD files from untrusted or unverified sources, creating the attack surface for this vulnerability
A user is affected if FastStone Image Viewer version 8.3 is installed and PSD files from any source can be opened, enabling the integer overflow trigger through a specially crafted file.
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 unverified PSD files in FastStone Image Viewer until an official patch is released. Consider using alternative image viewers or sandboxing the application for added isolation when handling files from unknown sources.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30041 — 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-30041 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