CVE-2025-4802VulnerabilityPublished 9 Jun 2025Updated 11 Oct 2026

SUSE · security update for glibc

Affects SUSESource GCVE Database

Not known to be exploited : upgrade to 9.4.12 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.4.12

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redhat/glibc to 9.4.12.

Affected software

Product	Affected	Fixed in
Red Hatredhat/glibc`pkg:rpm/redhat/glibc`Other threats	Affected =9.4 <9.4.12	Fixed in 9.4.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability and should be applied to affected systems. No effective mitigations other than patching currently meet Red Hat's criteria for ease of use and applicability. Users should ensure that any custom static setuid binaries are reviewed and updated accordingly. Red Hat strongly discourages the use of custom setuid programs due to inherent security risks.

Description

Red Hat Discovery, also known as Discovery, is an inspection and reporting tool that finds, identifies, and reports environment data, or facts, such as the number of physical and virtual systems on a network, their operating systems, and relevant configuration data stored within them. Discovery also identifies and reports more detailed facts for some versions of key Red Hat packages and products that it finds in the network.

Impact

If exploited, a local attacker could escalate privileges and execute arbitrary code with the privileges of the vulnerable static setuid binary. The flaw also poses risks to confidentiality and availability by potentially allowing unauthorized file reads or causing program crashes. However, exploitation requires a specific binary type (static setuid calling dlopen), which Red Hat does not ship by default, limiting the practical impact.

Summary

The vulnerability CVE-2025-4802 involves a flaw in the GNU C Library (glibc) where static setuid binaries that invoke dlopen(), including internal calls after setlocale() or NSS functions like getaddrinfo(), may improperly use LD_LIBRARY_PATH to locate shared libraries. This behavior can allow a local attacker to load malicious shared libraries, potentially escalating privileges and executing arbitrary code. Red Hat has not found any such vulnerable static setuid binaries in their Enterprise Linux distribution but acknowledges that custom setuid programs might exist. The issue is rated moderate severity and a patch is available to address it.

CWE-426Untrusted Search Path (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.
Architecture and Design · Implementation · Attack Surface Reduction
Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
Implementation
When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames.
Implementation
Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
OWASP Cheat Sheets
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
Attack patterns
Leveraging/Manipulating Configuration File Search Paths (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Aug 2026, 21:06 UTC

WeaknessesCWE-426

Technical details

References

Community reviews

Related threats