Critical Use-After-Poison Vulnerability in libjpeg-turbo

libjpeg-turbo Updated 20 Jan 2026

Summary

20/01/2026
HIGH
Yes i
High
Not published

OSV-2026-91: Use-after-poison in compress.cc. Affects libjpeg-turbo versions >= 43b0c0536bde8d367f5031e7990228928650c5b3, < 3eb879acf4ce1efb4750688e864af172d34a4e0a. Fixed in 3eb879acf4ce1efb4750688e864af172d34a4e0a. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libjpeg-turbo is an open-source library that provides a high-speed implementation of JPEG image compression and decompression. It is widely used in various applications for handling JPEG images due to its efficiency and performance. However, like many software libraries, it can be susceptible to vulnerabilities that may compromise its functionality and security.

Vulnerability Detail

The vulnerability identified in libjpeg-turbo is a use-after-poison issue located in compress.cc. This type of vulnerability occurs when a program continues to use a memory location after it has been freed or marked as invalid, leading to potential crashes or exploitation. The specific crash type reported is a 'Use-after-poison READ 1', which indicates that the program attempted to read from a memory area that has been poisoned, resulting in undefined behavior. This vulnerability can lead to application crashes and may expose sensitive data, making it a critical issue that requires immediate attention.

How To Fix

Minimum fixed version

3eb879acf4ce1efb4750688e864af172d34a4e0a

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. It is recommended to update to the patched version as soon as possible to mitigate risks.

Conclusion

The use-after-poison vulnerability in libjpeg-turbo poses significant risks to applications that utilize this library. It is crucial for developers to update to the patched version to ensure the security and stability of their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for libjpeg-turbo →

Share this vulnerability

FAQ

A use-after-poison vulnerability occurs when a program continues to access memory that has been marked as invalid or freed, leading to potential crashes or exploitation.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By simply uploading your manifest file like package-lock.json, you can check if your application is affected.

The risks include application crashes, potential data exposure, and exploitation by malicious actors, which could compromise the security of the application.

Currently, there are no specific workarounds available. The best course of action is to update to the patched version as soon as possible.

Detailed information can be found in the OSS-Fuzz report linked in the vulnerability details, as well as on the official libjpeg-turbo GitHub repository.

Related vulnerabilities

Recent vulnerabilities recorded for libjpeg-turbo.

How To Fix

Minimum fixed version

3eb879acf4ce1efb4750688e864af172d34a4e0a

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback