Loading vulnerability…
CVE-2025-47256 is a stack-based buffer overflow in Libxmp through version 4.6.2. The flaw is in the depack_pha function in loaders/prowizard/pha.c and can be triggered by processing a malformed Pha format tracker module embedded in a .mod file. The vulnerability arises from improper bounds handling on stack-allocated memory during parsing/depacking of the crafted module data, which can cause a write beyond the bounds of a stack buffer.
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.
This repository provides a proof-of-concept (PoC) exploit for CVE-2025-47256, a stack-based buffer overflow in the depack_pha() function of the libxmp library. The repository contains two files: a README.md with detailed vulnerability and build information, and poc.c, a C program that loads a malicious Pha Packer module (embedded as a C array in poc_data.h) into libxmp using the xmp_load_module_from_memory() API. When executed, the PoC triggers the stack overflow, resulting in a crash (denial of service) and potentially remote code execution under certain conditions. The exploit is local and requires the user to compile and run the code on a system with libxmp. No network endpoints are involved; the main fingerprintable elements are the crafted module file and the vulnerable source file in libxmp.
4 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.