Skip to main content
VulnerabilityPublished Updated

CVE-2023-49990: espeak-ng · Classic Buffer Overflow

Affects espeak-ngSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubespeak-ng/espeak-ngpkg:github/espeak-ng/espeak-ngOther threatsAffected
  • =1.52-dev
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2023-49990, European organizations should: 1) Monitor Espeak-ng project repositories and security advisories for official patches or updates addressing this vulnerability and apply them promptly. 2) Restrict local access to systems running Espeak-ng, ensuring only trusted users can execute or interact with the software. 3) Implement application whitelisting and endpoint protection to detect anomalous behavior indicative of exploitation attempts. 4) Educate users about the risks of interacting with untrusted files or inputs that could trigger the vulnerability. 5) Where possible, sandbox or isolate speech synthesis processes to limit the impact of potential exploits. 6) Conduct code reviews and static analysis if maintaining custom builds of Espeak-ng to identify and remediate unsafe buffer handling. 7) Employ runtime protections such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to reduce exploitation success likelihood. 8) For embedded or specialized devices using Espeak-ng, coordinate with vendors to ensure firmware updates incorporate vulnerability fixes.

Description

Espeak-ng 1.52-dev was discovered to contain a buffer-overflow via the function SetUpPhonemeTable at synthdata.c.

References

Community reviews

Loading reviews…