CVE-2026-38641: relibc Denial of Service Vulnerability in mmap_and_copy
CVE-2026-38641 is a denial-of-service vulnerability in relibc's shared library loading mechanism. An attacker can craft a malicious shared library that, when loaded, crashes the affected application or service. The vulnerability requires no special privileges or user interaction, making it straightforward to exploit over a network. However, it does not compromise confidentiality or integrity—only availability.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-404
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-26 / 2026-06-29
NVD description (verbatim)
An issue in the DSO::mmap_and_copy function of relibc commit 61f42d allows attackers to cause a Denial of Service (DoS) via loading a crafted shared library.
5 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the DSO::mmap_and_copy function within relibc commit 61f42d. This function is responsible for memory-mapping and copying operations during shared library loading. A crafted shared library can trigger improper error handling or resource management in this function, causing an uncontrolled crash. The issue stems from insufficient validation or bounds-checking when processing library data, classified under CWE-404 (Improper Resource Validation).
Business impact
Services relying on relibc for dynamic library loading face availability risk. An unauthenticated remote attacker can disrupt operations without credentials or user action, leading to service downtime. This is particularly concerning for long-running daemons, containerized applications, or microservices that dynamically load libraries at runtime. Recovery requires manual intervention or automated restart mechanisms.
Affected systems
Any application or system built with or embedding relibc is potentially affected. Since relibc is a Rust standard library alternative used in certain embedded and systems programming contexts, impact is concentrated in projects explicitly adopting relibc. The lack of vendor or product metadata in the disclosure suggests this affects a narrower ecosystem than mainstream C/C++ runtimes; however, you should audit your supply chain for relibc dependencies.
Exploitability
Exploitability is high. The attack vector is network-based, requires no authentication or privileges, and demands no user interaction. An attacker need only cause an affected application to load a crafted shared library—this could occur through supply chain compromise (trojanized library), local file placement, or if the application dynamically loads libraries from attacker-controlled or insufficiently validated sources. The low complexity score reflects the straightforward nature of the attack.
Remediation
Update relibc to a patched commit beyond 61f42d. Verify the exact patched version against the relibc project's security advisories and release notes. Additionally, implement network segmentation to restrict which sources can deliver shared libraries to your applications, and use code signing or integrity verification for all dynamically loaded libraries.
Patch guidance
Monitor the relibc project repository and official security channels for patch releases. Once available, update your build or dependency manager (e.g., Cargo for Rust projects) to reference the fixed commit or release version. Test patches in a staging environment before production rollout. If you maintain custom builds of relibc, review the changes in commit 61f42d and apply the necessary fixes from upstream.
Detection guidance
Monitor for unexpected process crashes or restarts in applications using relibc, especially if correlated with new or modified shared library files in your environment. Log dynamic library loading attempts and their sources. Use host-based intrusion detection to flag attempts to load suspicious or unsigned libraries. In containerized environments, scan images for relibc and vulnerable commits during CI/CD.
Why prioritize this
This vulnerability merits prompt attention due to its high CVSS score (7.5), unauthenticated network exploitability, and denial-of-service impact. Although not yet in CISA's Known Exploited Vulnerabilities catalog, the low barrier to exploitation and availability impact justify rapid patching. Prioritize systems where relibc is a critical dependency and where downtime carries business cost.
Risk score, explained
The CVSS 3.1 score of 7.5 (HIGH) reflects the combination of network accessibility (AV:N), low attack complexity (AC:L), no authentication requirement (PR:N), no user interaction (UI:N), and high availability impact (A:H). The vulnerability does not affect confidentiality or integrity, which caps the severity below critical. The overall rating appropriately captures a serious but containable risk.
Frequently asked questions
How do I know if my project uses relibc?
Check your project's dependencies. In Rust/Cargo projects, search Cargo.toml and Cargo.lock for 'relibc'. For C/C++ projects, search build scripts and documentation for relibc references. relibc is not a default dependency in most projects; adoption is typically explicit. If unsure, consult your build system documentation.
Is this vulnerability being actively exploited?
As of the publication date (2026-06-26), this vulnerability has not been added to CISA's Known Exploited Vulnerabilities catalog, meaning no active exploitation has been officially documented. However, the low barrier to exploitation means you should not delay patching while awaiting evidence of in-the-wild attacks.
What if I can't update relibc immediately?
Implement compensating controls: restrict library loading sources, use code signing and integrity verification, run applications in sandboxes or containers with minimal privileges, and enable alerting on process crashes. Monitor for suspicious library files. These measures reduce risk but do not eliminate it; plan an expedited patch window.
Does this affect standard Linux or Windows systems?
relibc is a niche Rust runtime alternative, not part of the standard C library on Linux (glibc, musl) or Windows (MSVCRT). Impact is limited to applications explicitly built with relibc. Most Linux and Windows users are unaffected unless they use specialized Rust-based tools or embedded systems that opted into relibc.
This analysis is for informational purposes and does not constitute legal, compliance, or professional security advice. Verify all patch details, CVSS scores, and affected versions directly against the relibc project's official security advisories and vendor documentation. Test patches thoroughly in non-production environments before deployment. SEC.co does not guarantee the completeness or currency of this intelligence; consult primary sources for authoritative vulnerability data. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-10069HIGHShibby Tomato miniupnpd Resource Exhaustion Vulnerability
- CVE-2026-45174HIGHIdira Endpoint Privilege Manager Linux Agent Local Privilege Escalation
- CVE-2026-54280HIGHAIOHTTP Resource Leak on Client Disconnect (3.14.1+)
- CVE-2026-59725HIGHSocket.IO Engine.IO HTTP Polling Denial of Service
- CVE-2026-10113MEDIUMOpen5GS NF-Profile Parser Denial of Service Vulnerability
- CVE-2026-10115MEDIUMOpen5GS NF Profile Parser DoS Vulnerability
- CVE-2026-10116MEDIUMOpen5GS UE Authentication Denial-of-Service Vulnerability
- CVE-2026-10117MEDIUMOpen5GS nghttp2-server Denial of Service Vulnerability