CVE-2017-10926
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 · uneditedIrfanView 4.44 (32bit) with FPX Plugin 4.47 might allow attackers to cause a denial of service or possibly have unspecified other impact via a crafted .fpx file, related to a "Read Access Violation starting at wow64!Wow64NotifyDebugger+0x000000000000001d."
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 confidenceA memory corruption vulnerability exists in IrfanView 4.44 (32-bit) when processing crafted .fpx files through the FPX Plugin 4.47. The vulnerability triggers a read access violation at the wow64!Wow64NotifyDebugger function, leading to denial of service. The flaw is caused by insufficient validation of malformed FPX image file structures during 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= 4.44= 4.47CVSS 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.0/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.
-
Confirm IrfanView installation and bitnessLocate IrfanView installation directory (commonly C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView). Identify if running 32-bit version - check for irfanview.exe in Program Files (x86) or verify file properties showing 32-bit application.Affected if IrfanView 32-bit is installed in the system
-
Check IrfanView versionRight-click irfanview.exe, select Properties, go to Details tab. Alternatively, run 'irfanview.exe /?' or check Help > About in the application. Confirm version is 4.44.Affected if Installed version is exactly 4.44
-
Locate and verify FPX plugin versionNavigate to the 'plugins' subfolder within the IrfanView installation directory. Look for fpx.dll or FPX.dll. Right-click the file, select Properties > Details to check the version. Alternatively, in IrfanView go to Properties > Plugins to list loaded plugins with versions.Affected if FPX plugin version is 4.47
-
Confirm .fpx file association or capabilityIn IrfanView, attempt to open a .fpx file or check File > Open dialog by selecting 'FPX' file type. Also verify in IrfanView Properties > Plugins that the FPX plugin is enabled/loaded.Affected if FPX plugin is loaded and .fpx files can be opened in IrfanView
A user is affected if they have IrfanView 4.44 (32-bit) with FPX plugin 4.47 installed and the FPX plugin is enabled for processing .fpx image 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.
From vendor dataUpdate IrfanView and FPX Plugin to the latest versions, or restrict acceptance of .fpx files from untrusted sources until the patch is applied.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10926 — 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-2017-10926 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