CVE-2025-0395

When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.

Published: 2025-01-22 Last update: 2026-05-12 Assigner: 3ff69d7a-14f2-4f67-a097-88dee7810d18 Source: 3ff69d7a-14f2-4f67-a097-88dee7810d18

Conclusion & alert: CVE-2025-0395 is rated Low Risk (32.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.07%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-0395

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-02 0.02% 0.07% +0.05%
2 2026-02-05 0.65% 0.02% -0.62%
3 2025-12-31 0.65%

Full EPSS history (24 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-0395

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.5 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-0395

GitHub Security Advisory for CVE-2025-0395

GHSA-4xpw-6594-8f5m · Severity: high — When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate...

OS Trackers for CVE-2025-0395

vendor priority summary link
debian not yet assigned CVE-2025-0395 not yet assigned priority: Debian including 1 source packages (glibc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-0395
gentoo high CVE-2025-0395: 1 GLSA(s) (202505-06), 1 atom(s) (sys-libs/glibc); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-0395
redhat medium https://access.redhat.com/security/cve/CVE-2025-0395
suse low CVE-2025-0395 severity low: SUSE including 1042 source package names (0.0.17-1.1:glibc-2.38-150600.14.23.1, 0.1.6-1.2:glibc-2.38-150600.14.23.1, …), 3061 product×package rows across 498 product lines (Container bci/bci-busybox, Container bci/dotnet-aspnet, … (498 product lines)): Fixed 2814, Known Affected 221, First Fixed 13, Known Not Affected 13. https://www.suse.com/security/cve/CVE-2025-0395/
ubuntu medium CVE-2025-0395 medium priority: Ubuntu including 2 source packages (eglibc, glibc), 17 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): released 10, DNE 6, needs-triage 1. https://ubuntu.com/security/CVE-2025-0395

Affected software / configurations for CVE-2025-0395

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-0395

cvelogic Threat Intelligence