What is CVE-2026-49413?
The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.
The record classifies CVE-2026-49413 under weakness class CWE-266. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 100 days ago.
Severity and exploitation probability
- EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 3.7% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-06-27
Is CVE-2026-49413 being exploited?
Weaponised exploit code for CVE-2026-49413 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.
- ii4gsp/CVE-2026-49413 (github)
Affected products and versions
- FreeBSD: FreeBSD
How to fix CVE-2026-49413
No vendor patch reference has been recorded for CVE-2026-49413 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-49413
No threat campaign in the Threadlinqs corpus currently references CVE-2026-49413, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.