CVE-2026-49413

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
0.9%
KEV
Not listed

Published

June 27, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No patch confirmed yet.
generic
https://security.freebsd.org/advisories/FreeBSD-SA-26:30.linux.asc

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 10:39 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 23:22 UTCEG score recompute
  4. 2026-07-11 12:05 UTCEG score recompute
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 00:49 UTCEG score recompute
  7. 2026-07-10 13:33 UTCEG score recompute
  8. 2026-07-10 02:16 UTCEG score recompute
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 14:59 UTCEG score recompute
  11. 2026-07-09 03:42 UTCEG score recompute
  12. 2026-07-08 16:25 UTCEG score recompute
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 05:09 UTCEG score recompute
  15. 2026-07-07 17:49 UTCEG score recompute
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 06:29 UTCEG score recompute
  18. 2026-07-06 19:10 UTCEG score recompute
  19. 2026-07-06 07:53 UTCEG score recompute
  20. 2026-07-05 20:36 UTCEG score recompute
  21. 2026-07-05 09:19 UTCEG score recompute
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 22:02 UTCEG score recompute
  24. 2026-07-04 10:45 UTCEG score recompute
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 20 more
  1. 2026-07-03 23:25 UTCEG score recompute
  2. 2026-07-03 12:09 UTCEG score recompute
  3. 2026-07-03 00:31 UTCEG score recompute
  4. 2026-07-02 13:15 UTCEG score recompute
  5. 2026-07-02 01:57 UTCEG score recompute
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 14:40 UTCEG score recompute
  8. 2026-07-01 03:24 UTCEG score recompute
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 16:07 UTCEG score recompute
  11. 2026-06-30 04:51 UTCEG score recompute▲ 7.10
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 13:32 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 09:36 UTCNVD update
  19. 2026-06-27 09:15 UTCEG score recompute
  20. 2026-06-27 09:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49413?
CVE-2026-49413 is a high vulnerability published on June 27, 2026. The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the PSUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so ATSECURE was incorrectly set to zero for set-user-ID and set-group-ID executables.…
When was CVE-2026-49413 disclosed?
CVE-2026-49413 was first published in the National Vulnerability Database on June 27, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49413 actively exploited?
CVE-2026-49413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49413?
CVE-2026-49413 has a CVSS v3.1 base score of 7.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49413, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49413

Explore →

Is Your Infrastructure Affected by CVE-2026-49413?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs