Loading vulnerability…
CVE-2026-47754 is an unauthenticated path traversal vulnerability in Metacat affecting all 1.x releases and 2.x releases through 2.19.1. The flaw resides in the legacy 1.x API action=read endpoint, where ArchiveHandler.readArchiveEntry() incorporates the user-controlled archiveEntryName parameter into a filesystem path without proper validation or normalization. The vulnerable code path also lacks effective authorization enforcement because the surrounding read-permission check is commented out. As a result, a remote attacker can issue a single crafted GET request to traverse directories and read arbitrary files accessible to the Tomcat process hosting Metacat. The issue was removed in Metacat 3.0.0 when the legacy 1.x API, including the vulnerable archive handling component, was eliminated.
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.
action=read functionality exposed by the old API. Because the vulnerable API is generally unnecessary in modern deployments, removing or blocking access to those endpoints can substantially reduce or eliminate exposure. After changing servlet configuration or removing the legacy features, restart Tomcat or the servlet container to ensure the mitigation takes effect.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.