CVE-2013-6369: Stack-based buffer overflow in the jbg_dec_in function in libjbig/jbig.c in JBIG-KIT before 2.1 allows remo...

Security readout for executives and security teams

JBIG-KIT versions before 2.1 can crash, and may allow code execution, when an application processes a malicious JBIG image file. Business risk depends on where JBIG parsing occurs. Systems that accept images from users, email, scanning workflows, or automated document pipelines deserve priority review. Exposure is most likely in software or services using JBIG-KIT/libjbig before 2.1 to decode untrusted image content. The supplied affected-product metadata is incomplete, so vulnerability managers should check operating system packages, embedded dependencies, and image-processing applications. Prioritize remediation where JBIG image parsing is exposed to customers, email attachments, file uploads, or automated document intake. Treat internal-only, non-networked use as lower urgency after confirming no untrusted file path exists. Mitigation focus: Upgrade JBIG-KIT/libjbig to version 2.1 or a vendor-supported fixed package.; Check Linux distribution advisories for backported fixes and package names.; Limit processing of untrusted JBIG image files until remediation is complete..

Prepared

Jun 14, 2026, 14:32 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.