Skip to main content
VulnerabilityPublished

CVE-2026-4390: TeamSpeak 3 Server · Use After Free

Affects TeamSpeak 3 ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 3.13.8 : update TeamSpeak 3 Server when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.13.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
TeamSpeak 3 ServerAffected
  • 3.13.0 – 3.13.7
8 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:teamspeak_3_server:teamspeak_3_server:*:*:*:*:*:*:*:*

AI-suggested

Upgrade TeamSpeak 3 Server to version 3.13.8 or later, as this version contains the fix for the use-after-free vulnerability in the process_resend_queue function. No other mitigation steps are indicated or required according to the available data.

Description

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.

References

Community reviews

Loading reviews…