dbcve.org
GlibcFramework / library · Gnu

CVE-2025-4802

HIGH · 7.8 CVSS v3.1 Published 2025-05-16
Fix available
A fix is available. Upgrade to after 2.38 or later.
See remediation →
81/100
Remediation priority · High
Public exploit No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GlibcFramework / library
Affected:>= 2.27, <= 2.38

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.38
Vendor patch sourceware.org →
Recommended fix High confidence

glibc 2.39 or later (distributions may backport the fix to their own glibc-2.38 package versions)

  1. Identify the current glibc version installed: `ldd --version` or `glibc-version`
  2. Check if your distribution has a patched version available via package manager: `apt list --upgradable` (Debian/Ubuntu) or `yum check-update` (RHEL/CentOS)
  3. For Debian-based systems: `sudo apt-get update && sudo apt-get install libc6` to get the latest patched glibc
  4. For RHEL-based systems: `sudo yum update glibc` or `sudo dnf update glibc`
  5. For other distributions, consult vendor security advisories for distribution-specific patched glibc packages
  6. If building from source: clone glibc repository and checkout tag `glibc-2.39` or later, then rebuild and reinstall
  7. Verify the fix by confirming the patched glibc version is >= 2.39 or includes the commit 1e18586c5820e329f741d5c710275e165581380e
  8. Test critical setuid binaries (e.g., `sudo`, `su`, `passwd`) to ensure they function correctly after the update
Caveat Upgrading glibc can affect system compatibility; test in staging environment first as some legacy applications may have dependencies on specific glibc behavior

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4802 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data