CVE-2026-18495 — CVE & Security Advisory Radar

🎯 CVE-2026-18495 🇪🇺 EUVD

📄 .md Alle CVEs anzeigen ✕

CVE-2026-18495 | A flaw was found in libtiff. A heap-buffer overflow vulnerability exists in the `tiff2pdf` utility due to an integer truncation error when processing crafted BigTIFF files. An attacker can provide a specially crafted BigTIFF file, causing a 64-bit `StripByteCounts` value to be truncated to a 32-bit integer. This leads to an undersized memory allocation and a subsequent out-of-bounds memory copy, resulting in a crash and severe memory corruption.

A flaw was found in libtiff. A heap-buffer overflow vulnerability exists in the `tiff2pdf` utility due to an integer truncation error when processing crafted BigTIFF files. An attacker can provide a specially crafted BigTIFF file, causing a 64-bit `StripByteCounts` value to be truncated to a 32-bit integer. This leads to an undersized memory allocation and a subsequent out-of-bounds memory copy, resulting in a crash and severe memory corruption.

Klassifikation & Betroffenheit:

Red Hat Red Hat Hardened Images patch: 4.7.2-2.hum1

Improper Restriction of Operations within the Bounds of a Memory Buffer 🎯 High

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

🛡️ Empfohlene Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow prot…

Vollständige Definition bei MITRE ➔

⚔️ Typische Angriffsmuster (CAPEC):

CAPEC-10 · Buffer Overflow via Environment Variable… (High) CAPEC-14 · Client-side Injection-induced Buffer Ove… (High) CAPEC-24 · Filter Failure through Buffer Overflow (High) CAPEC-42 · MIME Conversion (High) CAPEC-44 · Overflow Binary Resource File (Very High) CAPEC-45 · Buffer Overflow via Symbolic Links (High) CAPEC-100 · Overflow Buffers (Very High) CAPEC-123 · Buffer Manipulation (Very High)

🧩 Ähnliche Schwachstellen (Hersteller/Klasse/Score-Band):

CVE-2026-85197 7.6 CVE-2026-18621 7.6 CVE-2026-19387 7.6 CVE-2026-16313 7.6 CVE-2026-56208 7.6

📰 Eigene Berichterstattung: ➔ CVE-2026-18495 | Red Hat libtiff tiff2pdf buffer overflow (WID-SEC-2026-3338)

📚 Referenzen & Quellen:

🇪🇺 Original-Eintrag (ENISA EUVD) 🇺🇸 NVD-Eintrag

Ausnutzungs-Zeitleiste:

Reserviert 2026

Veröffentlicht 09/2026

Heute 18.09.

CVSS-Vektor-Analyse: 6.1

AV · Angriffsvektor Lokal

AC · Komplexität Gering

PR · Privilegien Gering

UI · Interaktion Erforderlich

S · Scope Unverändert

C · Vertraulichkeit Gering

I · Integrität Gering

A · Verfügbarkeit Hoch

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H

Veröffentlicht:11.09.2026

Aktualisiert:16.09.2026 19:42

Assigner (CNA):redhat

EUVD-ID:EUVD-2026-76166

Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

Tier	2026-08-29	2026-09-17
≥90 %	4	0
≥50 %	4	0
≥10 %	3	0
<10 %	304	300

6.1 MEDIUM

🇪🇺 EUVD

EPSS

12%

CVE-2026-18495 💻 Lokal 🔑 Geringe Nutzerrechte nötig

Red Hat

CVE-2026-18495 | A flaw was found in libtiff. A heap-buffer overflow vulnerability exists in the `tiff2pdf` utility due to an integer truncation error when processing crafted BigTIFF files. An attacker can provide a specially crafted BigTIFF file, causing a 64-bit `StripByteCounts` value to be truncated to a 32-bit integer. This leads to an undersized memory allocation and a subsequent out-of-bounds memory copy, resulting in a crash and severe memory corruption.

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

11.09.2026

🛡️ Details ➔

Zero-Day & Vulnerability Intelligence Hub