PT-2025-45950 · Julia · Glib Jll
Published
2025-10-19
·
Updated
2025-10-19
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
An issue was discovered in GNOME GLib before 2.66.8. When g file replace() is used with G FILE CREATE REPLACE DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Glib Jll