openSUSE-SU-2026:21800-1 Security update for freeciv
Attackers can execute arbitrary code or cause denial of service by tricking users into opening crafted save files in Freeciv.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is openSUSE-SU-2026:21800-1?
openSUSE-SU-2026:21800-1 is a memory corruption vulnerability in freeciv, published on 7 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
This update for freeciv fixes the following issues:
Changes in freeciv:
freeciv 3.2.6:
- Fix Heap Buffer Overflow in worklist_load() via Crafted Save File (boo#1278695)
- Fix Out-of-Bounds Read in activities.order[] via Crafted Save File (boo#1278696)
- Fix some unit move legality checks and path finding issues
- Improve logging about player authentication
- Fix infinite audio loop in the client exit with the SDL3 audio
- Fix issue with displayed "turns to grow" for the city to be wrong after city shrank
- Made tech tree not to show buildings or governments which tech actually makes unavailable
- Bug fixes, translation updates, docummentation updates
freeciv 3.2.5:
- Fix No First City vs Currently has cities inconsistency on savegame loading
- AI: Enable rampage with more attack types
- Fixed floating point exception at air unit handling
- Clients: Display NeverProtects unit help in correct place
- gtk4: Fixed city trading
- qt: Fixed "Save Options pn Exit" toggle
- Miscellaneous changes to developer/install/ruleset docs
- Corrected encoding of the Hungarian translation
- Compatibility fixes for glibc-2.43, g++16, Qt-6.11
Which versions are affected by openSUSE-SU-2026:21800-1?
Linux distribution packages (1)
freeciv openSUSE:Leap 16.0 | All versions | 3.2.6-bp160.1.1 |
How do I fix openSUSE-SU-2026:21800-1?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is openSUSE-SU-2026:21800-1 being exploited?
There is no known exploitation of openSUSE-SU-2026:21800-1 in the wild and no public exploit code.