Alerts This Week
Warning Icon 1 1,295
Alerts This Week
Warning Icon 1 1,295

Gentoo GLSA-202506-05 high: GTK+ 3 search path code execution threat

gentoo
Calendar Grey June 12, 2025
Dist Gentoo Esm H88
A vulnerability in GTK+ 3 could permit the execution of arbitrary code; it is advisable to update to maintain security.
A vulnerability has been discovered in Gtk+, which can lead to arbitrary code execution.

Summary

A vulnerability has been discovered in GTK+ 3. Please review the CVE identifiers referenced below for details.

Topics%20covered

Topics Covered

security advisory gentoo code execution high gtk search path

Resolution

All GTK+ 3 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=x11-libs/gtk+-3.24.48"

References

[ 1 ] CVE-2024-6655 https://nvd.nist.gov/vuln/detail/CVE-2024-6655

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202506-05
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: High
Title: GTK+ 3: Search path vulnerability
Date: June 12, 2025
Bugs: #949825
ID: 202506-05

Topics%20covered

Topics Covered

security advisory gentoo code execution high gtk search path

Synopsis

A vulnerability has been discovered in Gtk+, which can lead to arbitrary code execution.

Background

GTK+ (GIMP Toolkit +) is a toolkit for creating graphical user interfaces.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected ------------- ------------ ------------ x11-libs/gtk+ < 3.24.48 >= 3.24.48

Impact

Please review the referenced CVE identifier for details.

Workaround

There is no known workaround at this time.

Your message here