CVE-2026-90556

7.8

Freeciv · Freeciv

Freeciv versions before 3.2.6 are susceptible to a heap buffer overflow in the worklist_load function, allowing memory corruption via maliciously crafted savegame files.

Executive summary

A heap buffer overflow vulnerability in Freeciv allows for potential memory corruption when loading malicious savegame files, posing a significant risk to system integrity.

Vulnerability

The application fails to properly validate the length of worklists during the processing of savegame files. An attacker can supply a crafted file that triggers a heap buffer overflow, allowing data to be written past the intended array boundaries into adjacent memory.

Business impact

Successful exploitation of this vulnerability can lead to memory corruption, which may result in application crashes or potentially arbitrary code execution under the context of the user or server operator. Given the CVSS score of 7.8, this is a high-severity issue that could lead to unauthorized system access or denial of service, significantly impacting the availability and reliability of Freeciv hosting environments.

Remediation

Immediate Action: Upgrade all Freeciv installations to version 3.2.6 or later to incorporate the necessary bounds checking for worklist processing.

Proactive Monitoring: Review server and application logs for unusual crashes or error messages associated with the loading of external savegame files.

Compensating Controls: Restrict the ability to load savegame files from untrusted sources, such as public game servers or unknown third-party contributors, until the software is updated.

Exploitation status

Public Exploit Available: No — there is no confirmed public exploit available.

Analyst recommendation

The severity of this heap overflow requires immediate attention to prevent potential exploitation. Administrators should prioritize the update to version 3.2.6 across all environments, as this provides the only definitive resolution to the underlying memory safety issue. Failure to patch may leave systems susceptible to memory corruption attacks triggered by seemingly benign savegame files.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Tristan Madani, per the CVE Program record.