Skip to main content

IrfanView CVE-2026-121517

| EUVDEUVD-2026-116380 LOW
Heap-based Buffer Overflow (CWE-122)
2026-11-03 VulDB GHSA-99fw-w5ph-h34w
1.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious TIFF Wang annotation
  2. Delivery
    Deliver file to victim
  3. Exploit
    Victim opens file in IrfanView
  4. Execution
    Overflow in annotation handler
  5. Impact
    Corrupt heap memory

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the IrfanView TIF-Annotations option be manually enabled - the vendor confirms this feature is OFF by default, so normal/default installations are not affected. The victim must then open an attacker-supplied TIFF file carrying a crafted Wang annotation (UI:P - passive user interaction), on IrfanView 4.76.0.0 / Win64. Limiting factors: high attack complexity (the vendor and VulDB both note exploitation is difficult), the non-default configuration requirement, and the need for the user to open the malicious file. No authentication is required (PR:N), but these conditions substantially constrain realistic exploitation.

Impact

Signals align toward low real-world priority rather than a contradiction. The supplied CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:N/UI:P) yields a base-equivalent score of only 1.3, driven by high attack complexity (AC:H), required passive user interaction (UI:P), and low impact to confidentiality, integrity, and availability (VC:L/VI:L/VA:L). The vuln.today decision label is 'monitor' (not act_now or emergency). This is NOT in CISA KEV - there is no confirmed active exploitation. EPSS is not provided in the input, so exploitation probability cannot be quantified. A public PoC reference exists (a GitHub writeup), but it is not verified as working exploit code, so it should not be equated with a reliable weaponized exploit. Crucially, the vendor confirms the vulnerable TIF-Annotations feature is OFF by default and rates the danger 'low,' meaning default installations are not exposed. The net picture is a genuinely low-priority issue: a high-CVSS class (heap overflow) that in practice is hard to exploit, limited to a non-default configuration, requires user interaction, and has only low assessed impact. No signals conflict here - severity, decision label, and vendor statement are consistent.

Exploit ScenarioDerived

An attacker crafts a malicious TIFF file containing a manipulated Wang annotation and delivers it to a victim (e.g., via email or a download) who has manually enabled the non-default TIF-Annotations option in IrfanView 4.76.0.0 on Win64. When the victim opens the file, the annotation handler triggers a heap-based buffer overflow. A public PoC reference exists but is not verified as working exploit code, and the high attack complexity means reliable exploitation is difficult.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

IrfanView 4.76.0.0 on Windows x64 has a heap-based buffer overflow (CWE-122) in its TIFF Wang Annotation handling: opening a crafted TIFF file that carries a malicious Wang annotation can corrupt heap memory. Exploitation is constrained - the TIF-Annotations feature is disabled by default and must be explicitly enabled by the user, and both the vendor and VulDB characterise successful triggering as difficult; no authentication is needed but the victim must open the attacker-supplied file. A public PoC reference exists (a GitHub write-up under dwBruijn/CVEs), but it is not verified as working exploit code; the CVSS 4.0 score is 1.3 and the priority label is 'monitor', consistent with a low real-world risk rather than an urgent one.

RemediationAI

The vendor-recommended action is to apply the available patch/update for IrfanView from https://www.irfanview.com/ - the input confirms a fix is recommended and available but does not state an exact fixed version number, so the installed build should be checked against the current release on the vendor site. Because the vulnerable code path is the TIFF Wang annotation parser, the practical compensating control for users who cannot update immediately is to keep the TIF-Annotations option disabled (the default), which removes exposure at the cost of losing TIFF annotation display; this is a configuration change the vendor itself cites as the reason normal users are unaffected. Users who require annotation support should treat TIFF files as untrusted input until the update is applied. No further mitigations are specified in the supplied evidence.

Affected VersionsENISA

Irfanview 4.76.0.0

Affected Packages

euvd irfanview no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IrfanView is a Windows image viewer whose TIFF import path includes support for Wang annotations - an extension embedded in TIFF files (originally used by Wang imaging systems) that stores free-form annotation objects alongside image data. The flaw is a heap-based buffer overflow (CWE-122), meaning a length or size value taken from the annotation structure is not adequately validated against the size of an allocated heap buffer before data is written, allowing out-of-bounds writes on the heap. The affected CPE entry is a wildcard for IrfanView, and the report is specific to version 4.76.0.0 on Win64. The supplied evidence does not describe the exact parsing routine or the specific annotation field that is mishandled, so the precise trigger mechanism is not described in the available sources. The CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:N/UI:P) and the assessed CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L) both describe network-delivered input requiring the user to open a file, with high attack complexity and limited confidentiality, integrity and availability impact confined to the application.

Know when Irfanview gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 1.3 LOW
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 5.0 MEDIUM

Remote malicious file but difficult to exploit and dependent on a non-default feature (AC:H); no auth (PR:N) yet requires the user to open the file (UI:R); impacts assessed low per the evidence.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Nov 03, 2026 - 21:22 NVD
2.3 (LOW) 1.3 (LOW)
CVE Published
Nov 03, 2026 - 21:00 cve.org
LOW 1.3

DescriptionCVE.org

A vulnerability was detected in IrfanView 4.76.0.0 on Win64. Affected by this vulnerability is an unknown functionality of the component TIFF Wang Annotation Handler. Performing a manipulation results in heap-based buffer overflow. The attack is possible to be carried out remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit is now public and may be used. It is recommended to apply a patch to fix this issue. The vendor confirms: "[T]he TIF-Annotations option is OFF by default. Means, normal users are not affected ... the danger level for this is low".

Threat Intelligence Overview

Prevalence
Medium
popular free Windows image viewer, common but not universally deployed
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS N/A
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +6
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

CVE-2012-0897 MEDIUM POC
6.8 Jan 20

Stack-based buffer overflow in the JPEG2000 plugin in IrfanView PlugIns before 4.33 allows remote attackers to execute a

CVE-2012-3585 CRITICAL POC
9.3 Jul 05

Heap-based buffer overflow in jpeg_ls.dll in the Jpeg_LS (aka JLS) plugin in the formats plugins in IrfanView PlugIns be

CVE-2012-0278 CRITICAL POC
9.3 Apr 18

Heap-based buffer overflow in the FlashPix PlugIn before 4.3.4.0 for IrfanView might allow remote attackers to execute a

CVE-2012-0025 MEDIUM POC
6.8 Nov 02

Double free vulnerability in the Free_All_Memory function in jpeg/dectile.c in libfpx before 1.3.1-1, as used in the Fla

CVE-2021-27362 CRITICAL POC
9.8 Feb 17

The WPG plugin before 3.1.0.0 for IrfanView 4.57 has a Read Access Violation on Control Flow starting at WPG!ReadWPG_W+0

CVE-2019-16887 HIGH POC
7.8 Sep 25

In IrfanView 4.53, Data from a Faulting Address controls a subsequent Write Address starting at image00400000+0x00000000

CVE-2019-13243 HIGH POC
7.8 Jul 04

IrfanView 4.52 has a User Mode Write AV starting at image00400000+0x00000000000249c6. Rated high severity (CVSS 7.8), th

CVE-2019-13242 HIGH POC
7.8 Jul 04

IrfanView 4.52 has a User Mode Write AV starting at image00400000+0x0000000000013a98. Rated high severity (CVSS 7.8), th

CVE-2021-27224 HIGH POC
7.5 Feb 17

The WPG plugin before 3.1.0.0 for IrfanView 4.57 has a user-mode write access violation starting at WPG+0x0000000000012e

CVE-2020-35133 HIGH POC
7.5 Dec 16

irfanView 4.56 contains an error processing parsing files of type .pcx. Rated high severity (CVSS 7.5), this vulnerabili

CVE-2013-6932 HIGH
7.6 Dec 28

Buffer overflow in IrfanView before 4.37, when a multibyte-character directory name is used, allows user-assisted remote

CVE-2020-13880 CRITICAL
9.8 Jan 05

IrfanView B3D PlugIns before version 4.56 has a B3d.dll!+1cbf heap-based out-of-bounds write. Rated critical severity (C

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy