CVE-2021-28153

What it is

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.)

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-03-11 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-14 12:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.7% in the next 30 days (EPSS).
• Severity: 5.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-03-11 22:15 UTC

Last modified

2026-10-14 12:17 UTC

Exploit probability

2.7% · EPSS, next 30 days

Weakness

CWE-59

Record status

Modified

Affected

• Gnome Glib < 2.66.8
• Broadcom Brocade Fabric Operating System Firmware
• Debian Linux 9.0
• Fedoraproject Fedora 33

Attack profile CVSS 3.1 · 5.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2021-28153.md and follow it. Check whether this project is affected by CVE-2021-28153. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge