dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-4390

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
A weakness has been identified in TeamSpeak 3 Server up to 3.13.7. This affects the function process_resend_queue of the component Connection State Management. This manipulation causes use after free. The attack may be initiated remotely. Upgrading to version 3.13.8 is able to mitigate this issue. The affected component should be upgraded.

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 · moderate confidence

A use-after-free vulnerability exists in TeamSpeak 3 Server's Connection State Management component, specifically in the process_resend_queue function. This memory corruption issue in the connection state handling can be exploited remotely to potentially execute arbitrary code or cause service disruption.

MitigationUpgrade TeamSpeak 3 Server from any version up to 3.13.7 to version 3.13.8 or later to address the use-after-free vulnerability in the connection state management.

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

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
Low
Availability
Low

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

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 TeamSpeak 3 Server installation
    Locate the ts3server binary or check running processes for ts3server. On Linux, run `ps aux | grep ts3server` or check the server installation directory.
    Affected if No TeamSpeak 3 Server process is found (not affected)
  2. Determine installed server version
    Run `ts3server --version` from the server binary directory, or check the server startup log file (usually logs/ts3server*.log) for the version line printed at startup.
    Affected if Version cannot be determined from available binaries or logs
  3. Compare version against affected range
    Compare the installed version to the affected range: any version up to 3.13.7 is vulnerable. Version 3.13.8 and later are fixed. Example: if version shows 3.13.7 or lower, it is within the affected range.
    Affected if Installed version is 3.13.7 or lower, or any version prior to 3.13.8
  4. Verify server is accepting connections
    Confirm the TeamSpeak 3 Server is running and accessible. Check that the server process is active and listening on the default voice port (9987 UDP) or configured ports.
    Affected if Server is running and accepting client connections - the vulnerable connection state management code is active

If the installed TeamSpeak 3 Server version is 3.13.7 or lower and the server is running and accepting connections, the environment is affected by this use-after-free vulnerability in the connection state management.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TeamSpeak 3 Server from any version up to 3.13.7 to version 3.13.8 or later to address the use-after-free vulnerability in the connection state management.

Recommended fix High confidence

TeamSpeak 3 Server 3.13.8

  1. 1. Identify the currently running TeamSpeak 3 Server version using the server query or checking server logs
  2. 2. Download TeamSpeak 3 Server version 3.13.8 or later from the official TeamSpeak download page (www.teamspeak.com) or files.teamspeak-services.com
  3. 3. Stop the TeamSpeak 3 Server service/process
  4. 4. Create a complete backup of the TeamSpeak 3 Server installation directory and all data including the ts3server.sqlite database and configuration files
  5. 5. Extract and install the new version 3.13.8 files to replace the old installation
  6. 6. Restore any custom configuration files from the backup if needed
  7. 7. Start the TeamSpeak 3 Server service
  8. 8. Verify the server is running the patched version by connecting as a server admin and checking the server version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4390 — 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-2026-4390 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