Skip to main content
VulnerabilityPublished

CVE-2025-53964: goldendict · Exposed Dangerous Method or Function

Affects goldendictSource CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jul 2025

  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
GitHubgoldendict/goldendictpkg:github/goldendict/goldendictOther threatsAffected
  • >=1.5.0 <=1.5.1
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 the risks posed by CVE-2025-53964, European organizations should implement several specific measures beyond generic advice: 1) Immediately audit all systems for the presence of GoldenDict versions 1.5.0 and 1.5.1 and restrict or disable its use where possible until a patch is available. 2) Educate users about the risks of adding untrusted or unknown dictionaries to GoldenDict, emphasizing the dangers of opening files from unverified sources. 3) Implement application whitelisting or sandboxing for GoldenDict to limit its file system access and prevent unauthorized file modifications. 4) Monitor file system activity for unusual read/write operations originating from GoldenDict processes, using endpoint detection and response (EDR) tools. 5) Network segmentation should be used to isolate systems running GoldenDict from critical infrastructure to reduce lateral movement risk. 6) Stay updated with vendor announcements for patches or official fixes and apply them promptly once available. 7) Consider deploying intrusion detection systems (IDS) with signatures or heuristics to detect attempts to exploit this vulnerability. These targeted mitigations will reduce the attack surface and help prevent exploitation until a formal patch is released.

Description

GoldenDict 1.5.0 and 1.5.1 has an exposed dangerous method that allows reading and modifying files when a user adds a crafted dictionary and then searches for any term included in that dictionary.

References

Community reviews

Loading reviews…