CVE-2019-19126: On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable duri
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: glibc (Debian:10) 2.28-10+deb10u2; glibc (Debian:12) 2.29-8; glibc (Red Hat:enterprise_linux:7::client) 0:2.17-317.el7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to glibc (Debian:10) 2.28-10+deb10u2; glibc (Debian:12) 2.29-8; glibc (Red Hat:enterprise_linux:7::client) 0:2.17-317.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program.
- Published
- Nov 19, 2019
- Updated
- Oct 14, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-665
Report tools
Action score
13
Monitor
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | glibc | cpe:2.3:a:gnu:glibc |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.10
- debian debian linux10.0
- fedoraproject fedora30
- fedoraproject fedora31
- gnu glibcbefore 2.31
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | glibc | before 2.28-10+deb10u2 | 2.28-10+deb10u2 |
| Debian:12 | glibc | before 2.29-8 | 2.29-8 |
| Red Hat:enterprise_linux:7::client | glibc | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-common | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-debuginfo | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-debuginfo-common | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-devel | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-headers | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-static | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | glibc-utils | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:7::client | nscd | before 0:2.17-317.el7 | 0:2.17-317.el7 |
| Red Hat:enterprise_linux:8::appstream | compat-libpthread-nonshared | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::appstream | glibc-debuginfo | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::appstream | glibc-debuginfo-common | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::appstream | glibc-utils | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-all-langpacks | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-common | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-devel | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-headers | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-langpack-aa | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-langpack-af | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-langpack-agr | before 0:2.28-101.el8 | 0:2.28-101.el8 |
| Red Hat:enterprise_linux:8::baseos | glibc-langpack-ak | before 0:2.28-101.el8 | 0:2.28-101.el8 |
+96
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4911Glibc: buffer overflow in ld.so leading to privilege escalationKEV80Now
- CVE-2015-0235Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-depen68This week
- CVE-2015-7547Multiple stack-based buffer overflows in the (1) send_dg and (2) send_vc functions in the libresolv library in the GNU C Library (aka glibc 60This week
Published before and after this one in the same product
- ← EarlierCVE-2019-1010024Jul 15, 2019 · GNU Libc current is affected by: Mitigation bypass.22Monitor
- ← EarlierCVE-2019-1010025Jul 15, 2019 · GNU Libc current is affected by: Mitigation bypass.22Monitor
- Later →CVE-2020-10029Mar 4, 2020 · The GNU C Library (aka glibc or libc6) before 2.32 could overflow an on-stack buffer during range reduction if an input to an 80-bit long do22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:glibc | 2.29-8 · Debian:12 | Package registry (OSV) |
| red hat:compat-libpthread-nonshared | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glibc | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-all-langpacks | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-common | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-debuginfo | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glibc-debuginfo-common | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glibc-devel | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-headers | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-langpack-aa | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-langpack-af | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-langpack-agr | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:glibc-utils | 0:2.28-101.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| suse:glibc | 2.26-13.36.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-905 · Oct 30, 2020(OpenShift Güvenlik Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-665 · Improper InitializationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4FQ5LC6JOYSOYFPRUZ4S45KL6IP3RPPZ/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZFJ5E7NWOL6ROE5QVICHKIOUGCPFJVUH/
- sourceware.org/bugzilla/show_bug.cgi?id=25204
- usn.ubuntu.com/4416-1/
- cert-portal.siemens.com/productcert/html/ssa-398330.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.