dbcve.org
WingsApplication · Pterodactyl

CVE-2025-69199

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-19
Fix available
A fix is available. Upgrade to 1.12.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to version 1.12.0, websockets within wings lack proper rate limiting and throttling. As a result a malicious user can open a large number of connections and then request data through these sockets, causing an excessive volume of data over the network and overloading the host system memory and cpu. Additionally, there is not a limit applied to the total size of messages being sent or received, allowing a malicious user to open thousands of websocket connections and then send massive volumes of information over the socket, overloading the host network, and causing increased CPU and memory load within Wings. Version 1.12.0 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Wings (Pterodactyl's server control plane) prior to version 1.12.0 lacks proper rate limiting and message size throttling on websocket connections. An attacker can open thousands of websocket connections and send excessive volumes of data, causing network saturation, memory exhaustion, and CPU overload on the host system.

MitigationUpgrade Wings to version 1.12.0 or later, which implements proper websocket rate limiting and message size constraints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WingsApplication
Affected:< 1.12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Wings version
    Run 'wings --version' or check the wings binary version on the host system
    Affected if The installed version is prior to 1.12.0 (versions like 1.11.x, 1.10.x, etc.)
  2. Verify Wings is managing nodes with websocket access
    Check Wings configuration file (usually /etc/pterodactyl/config.yml) for node and daemon settings that enable websocket connections to the panel
    Affected if Websocket connections are enabled and accessible from the network (default behavior)
  3. Inspect websocket connection activity
    Monitor active websocket connections using system tools like 'ss -tn' or 'netstat' on the port Wings listens on (usually 8080 or 8443 for daemon)
    Affected if Thousands of concurrent websocket connections are observed or connection count is unusually high for your expected workload
  4. Check for memory and CPU stress on Wings host
    Review system resource usage (free -m, top, or similar) on the Wings host
    Affected if Memory usage is abnormally high or CPU is saturated without corresponding legitimate workload increases

You are affected if Wings version is below 1.12.0 and websocket connections are exposed, particularly if you observe excessive websocket connections or resource exhaustion on the Wings host.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.12.0 or later
Fixed in 1.12.0
Interim mitigation

Upgrade Wings to version 1.12.0 or later, which implements proper websocket rate limiting and message size constraints.

Recommended fix High confidence

Wings 1.12.0

  1. Back up your current Wings configuration and data
  2. Download Wings version 1.12.0 from the official Pterodactyl GitHub repository or use your package manager to upgrade
  3. Stop the currently running Wings service
  4. Install the upgraded Wings package
  5. Verify the installation was successful by checking the Wings version
  6. Start the Wings service and verify websocket connections are functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69199 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data