Loading story…
A review of a FlappyPig-operated CTF platform found that it used Apache Shiro 1.2.4's CookieRememberMeManager with a hard-coded AES key. The key allowed an authorized researcher to decrypt and forge serialized RememberMe cookies, triggering unsafe Java deserialization on the server.
Standard CommonsCollections gadget chains were impeded by Shiro's custom class-loading behavior, but a URLDNS payload confirmed deserialization. The researcher then used a JRMPClient gadget chain with a malicious JRMP listener to achieve remote command execution; the issue was disclosed to FlappyPig before the write-up was published.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
An authorized review of FlappyPig's CTF platform identified a hard-coded Apache Shiro RememberMe AES key that enabled forged serialized cookies. The researcher used a JRMPClient payload and malicious JRMP listener to obtain shell access, and reported the vulnerability to FlappyPig before publication.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A researcher disclosed a four-vulnerability chain that enabled unauthenticated remote code execution on GitHub Enterprise versions before `2.8.7`. The attack began with a WebHook server-side request forgery (SSRF) bypass using an unusual IP-address representation to evade Faraday restrictions, then used a second SSRF flaw to reach the internal Graphite service. A CRLF injection in Python's `HTTPConnection` allowed protocol smuggling to internal Memcached, where an attacker could plant a malicious Ruby Marshal object in cache. When GitHub Enterprise deserialized the poisoned object, it executed attacker-controlled commands. GitHub validated the report and released version `2.8.7`, adding SSRF and internal network-access protections.
Sep 3, 2026
**JFrog Security** published a full exploit chain for a high-severity Redis stack buffer overflow, **CVE-2025-62507** (CVSS 8.8), affecting **Redis 8.2.0–8.2.2**. The flaw is in the new `XACKDEL` command, where Redis fails to bounds-check the number of message IDs copied into a fixed-size stack array, enabling attacker-controlled overwrite of stack memory and potential control of the return address. The research also highlighted that the *official Redis Docker image* was compiled **without stack canary protections**, materially lowering exploitation difficulty and enabling practical **remote code execution (RCE)** via return-oriented techniques. Separately, a critical remote command-injection issue was reported in **Apache bRPC**’s built-in heap profiler service, **CVE-2025-60021**, affecting **all versions prior to 1.15.0**. The `/pprof/heap` endpoint fails to sanitize the `extra_options` parameter before it is incorporated into command execution for jemalloc profiling, allowing **unauthenticated** attackers to execute arbitrary system commands with the bRPC process’s privileges when the endpoint is exposed to untrusted networks. Recommended remediation is to **upgrade to Apache bRPC 1.15.0+** or otherwise disable/restrict access to the vulnerable profiling endpoint in affected deployments.
Jun 29, 2026
A bug bounty researcher chained an XML External Entity (XXE) flaw with a ZIP directory-traversal vulnerability in an unnamed Java web application that accepted a custom ZIP-based `.xyz` package. The application extracted uploaded archives and parsed an XML manifest, allowing a locally referenced external entity to expose `/etc/hosts` and support further directory enumeration. After identifying an application JSP template, the researcher used the archive extraction flaw—commonly known as **Zip Slip**—to overwrite it with a web shell, achieving remote code execution once cached content expired. The case demonstrates how unsafe XML parser defaults and insufficient archive-path validation can turn file-upload functionality into server compromise; the organization reportedly remediated the findings within 12 hours.
Sep 3, 2026