Loading story…
Pterodactyl Wings patched a high-severity flaw, tracked as CVE-2026-52855, that allowed low-privileged users to read sensitive node configuration data through {{config.}} placeholders in egg configuration-file templates. In affected versions prior to 1.12.3, the templating mechanism exposed values from the full daemon configuration, including secrets such as config.token, config.token_id, and Docker registry settings, creating a path for credential disclosure and broader compromise.
The fix, shipped in Wings 1.12.3, changes templating to use a reduced configuration structure instead of the full runtime configuration. The associated code update limits substitutions to a narrower set of Docker-related fields and blocks replacement of entire JSON objects or arrays, allowing only scalar values to be templated. The vulnerability carries a CVSS 3.1 score reflecting network exploitation with low privileges and high impact to confidentiality, integrity, and availability.
See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
The vulnerability CVE-2026-52855 was newly received by security-advisories@github.com, describing how low-privileged users in Wings versions prior to 1.12.3 could read sensitive daemon configuration values through {{config.}} placeholders in egg configuration-file templates. The disclosure notes the issue is fixed in Wings 1.12.3 and references the fixing commit and GitHub security advisory.
A Pterodactyl Wings commit changed egg templating to use a reduced configuration structure and to block substitution of whole JSON objects or arrays. The patch limits templating exposure to selected Docker network interface values instead of the full daemon configuration.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
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.
**CISA** added **Wing FTP Server** vulnerability `CVE-2025-47813` to its **Known Exploited Vulnerabilities (KEV)** catalog, warning that the flaw is being actively exploited and requiring Federal Civilian Executive Branch agencies to remediate it by **March 30, 2026** under **BOD 22-01**. The issue affects Wing FTP Server versions prior to **7.4.4** and stems from improper handling of an overly long `UID` cookie in `loginok.html`, which can cause the server to disclose the application's full local installation path during web authentication. Although `CVE-2025-47813` is an **information disclosure** issue rather than a standalone remote code execution bug, reporting indicates it can support attacker reconnaissance and may be chained with other Wing FTP Server flaws in broader attack paths. The vendor patched the vulnerability in **May 2025** in version **7.4.4**, alongside **`CVE-2025-47812`** and **`CVE-2025-27889`**, and researcher **Julien Ahrens** previously published proof-of-concept details showing how the path disclosure could aid exploitation. Organizations using Wing FTP Server, not just federal agencies, should verify they are no longer running vulnerable versions and review exposure of web-based authentication components.
Jun 29, 2026
Attackers are actively exploiting **Wing FTP Server** vulnerability `CVE-2025-47812`, a critical remote code execution flaw affecting versions prior to **7.4.4** on Windows, Linux, and macOS. The bug stems from improper null-byte handling in the `username` parameter of the `loginok.html` web interface, allowing unauthenticated or anonymous attackers to inject malicious **Lua** code into session files and trigger execution when the application processes that data, resulting in **root** access on Linux or **NT AUTHORITY\SYSTEM** on Windows. Incident reporting shows exploitation began shortly after public disclosure, with attackers probing exposed servers, running reconnaissance commands, creating local user accounts for persistence, attempting payload delivery with `certutil`, using `cURL` for possible data exfiltration, and trying to deploy **ScreenConnect** through malicious Lua files. In one observed case, Microsoft Defender blocked a downloaded payload as **`Trojan:Win32/Ceprolad.A`**, and the affected `WFTPServer.exe` process later crashed before the host was isolated. Defenders are being urged to upgrade immediately to **7.4.4** or later and review session `.lua` files, session directories, and domain logs for signs of compromise.
Jul 24, 2026
Paperclip, an open-source control plane for AI agent teams, patched a **critical authorization bypass** tracked as `CVE-2026-41679` that could let a remote attacker self-register on exposed instances, obtain board-level API access, and execute arbitrary commands on the host running the service. The issue affected network-accessible deployments using Paperclip’s default authenticated-mode configuration, where missing authorization checks allowed an attacker to create and approve a CLI challenge, gain a persistent credential, and abuse a company import path that should have been restricted to instance administrators. By importing a crafted `.paperclip.yaml` file, an attacker could define an agent and command that would be executed by a host-level adapter with the permissions of the Paperclip server process. Paperclip also fixed two additional flaws reported by Oasis Security: `GHSA-x8hx-rhr2-9rf7`, a DNS rebinding issue in default `local_trusted` mode that could enable local command execution on developer machines, and `GHSA-xfqj-r5qw-8g4j`, which exposed issue data, skill documentation, and deployment details through missing authentication and authorization checks on several API routes. The fixes were released in source tag **`v2026.416.0`**, and operators were advised to upgrade to that version or later. Public exploit code has increased risk, including a Rapid7 Metasploit module for `CVE-2026-41679`, while reporting cited proof-of-concept exploitation but no confirmed active exploitation in the wild at the time of publication.
Aug 6, 2026