Loading vulnerability…
CVE-2025-31129 is an unsafe deserialization vulnerability in the Jooby web framework's pac4j integration, specifically in io.jooby.internal.pac4j.SessionStoreImpl#get within the io.jooby:jooby-pac4j component. The vulnerable code path deserializes untrusted session data. According to the advisory, attacker-controlled session values beginning with the prefix "b64~" may be treated as serialized content and deserialized by the application. This creates a classic deserialization-of-untrusted-data condition in which crafted input can trigger execution of attacker-influenced object graphs during session retrieval. The issue affects vulnerable 2.x and 3.x releases and is fixed in 2.17.0 and 3.7.0.
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 an exploit for CVE-2025-31129, targeting Java applications that use Apache Commons Collections 3.2.1 and are vulnerable to unsafe deserialization. The main exploit logic is in 'src/main/java/org/example/Main.java', which constructs a malicious serialized object using a chain of transformers. This chain, when deserialized by a vulnerable application, results in arbitrary code execution. The included payload demonstrates execution of the 'calc' program via a class file ('evilclass'), but the payload can be replaced with any arbitrary bytecode. The exploit requires the attacker to supply the crafted serialized object to the target application, typically over a network interface that accepts serialized Java objects. The repository also includes a helper class ('evil.java') that demonstrates a static initializer running 'calc', and a simple compile helper. The structure is typical for a Java deserialization exploit, and the code is operational, allowing for payload customization.
2 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.