Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-52855.

Unlock with Pro - from £29/user/mo
CVE-2026-52855 Microsoft Sentinel · KQL

Detect Pterodactyl Wings Egg Configuration-File Templating Node Secret Exposure (CVE-2026-52855) in Microsoft Sentinel

Detects exploitation of CVE-2026-52855, a critical (CVSS 9.9) information disclosure vulnerability in Pterodactyl Wings prior to 1.12.3. The Wings daemon's egg configuration-file templating engine fails to properly scope variable substitution, allowing a malicious or crafted egg/server configuration to reference and render node-level secrets (e.g., the Wings daemon token, SFTP credentials, Docker/panel authentication secrets) into server-accessible configuration files. An attacker with the ability to create or modify an egg (via panel admin compromise, supply-chain egg import, or a malicious server owner in multi-tenant environments) can exfiltrate node configuration secrets, leading to full node takeover. Detection focuses on Wings daemon logs showing configuration-file template rendering events that reference sensitive node config keys, unexpected egg install/import activity, and outbound access to rendered server config files containing daemon secrets.

MITRE ATT&CK

Tactic
Collection Credential Access Privilege Escalation

KQL Detection Query

Microsoft Sentinel (KQL)
kusto
let SuspiciousEggKeywords = dynamic(["config.token", "daemon_token", "docker.socket", "sftp.password", "authentication_token", "panel_secret"]);
ContainerLogV1
| where ContainerImageName has "wings" or ContainerName has "wings"
| where LogMessage has_any ("egg", "config-file template", "config file render")
| where LogMessage has_any (SuspiciousEggKeywords)
| extend NodeName = tostring(split(ContainerName, "_")[0])
| project TimeGenerated, NodeName, ContainerName, LogMessage
| order by TimeGenerated desc
critical severity medium confidence

Hunts Wings container/daemon logs (ingested via Container Insights or custom log forwarding) for configuration-file template rendering events that reference sensitive node-level secret keys, indicative of CVE-2026-52855 exploitation.

Data Sources

Container logsCustom application logs (Wings daemon)

Required Tables

ContainerLogV1

False Positives & Tuning

  • Legitimate egg developers debugging config templates with verbose logging
  • Automated egg validation/test pipelines that render configs for QA
  • Log noise from unrelated services matching keyword substrings

Other platforms for CVE-2026-52855


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate malicious egg config_files template referencing secret key

    Expected signal: Wings daemon logs recording config-file template rendering for the test egg, including reference to the config.token variable

  2. Test 2Render server config and inspect for exposed daemon secret

    Expected signal: File write event on server.properties under the server volume, plus Wings daemon log entry for config sync of the test server

  3. Test 3Verify unpatched Wings version is vulnerable

    Expected signal: Command execution log/audit entry for the wings version check on the lab host

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-52855 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections