Loading vulnerability…
CVE-2025-53367 affects DjVuLibre prior to version 3.5.29. The vulnerability is in the MMRDecoder::scanruns method, which fails to verify that the xr pointer remains within the bounds of the allocated buffer during processing. As a result, the method can perform writes past the end of the heap-allocated buffer, causing heap corruption. The same bounds-checking flaw can also permit an out-of-bounds read via the pr pointer. The issue is triggered while decoding crafted DjVu content and was fixed in DjVuLibre 3.5.29.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a minimal C++ proof-of-concept exploit for a heap out-of-bounds write vulnerability in DjVuLibre's MMRDecoder::scanruns function. The exploit is implemented in a modular fashion, with the main logic in 'source/lib.cpp' and 'source/lib.hpp', and the entry point in 'source/main.cpp'. The exploit works by generating a specially crafted DjVu file ('minimal.pdf') containing a malicious MMR chunk with a sequence of 0-length horizontal runs, which, when parsed by a vulnerable DjVuLibre installation, will trigger the OOB-write. The code is not weaponized and is intended for research and educational purposes, allowing users to reproduce and analyze the vulnerability. The repository includes build scripts (CMake), documentation, and test scaffolding, but the core exploit logic is in the C++ source files. No network or remote attack vectors are present; the attack is file-based, requiring the target to open the crafted DjVu file.
18 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.