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 97% 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 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)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
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 10× in last 7d / 50× 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-08-27 22:51 UTCEG score recompute
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-26 14:46 UTCEPSS rescore
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 21:46 UTCEG score recompute
  6. 2026-08-23 08:31 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 09:15 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 04:54 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 06:04 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 23:27 UTCEG score recompute
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 02:11 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 03:39 UTCEG score recompute
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 05:07 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 06:32 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 20:44 UTCEG score recompute
Show 57 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 22:12 UTCEG score recompute
  3. 2026-08-11 10:49 UTCEG score recompute
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 01:00 UTCEG score recompute
  6. 2026-08-09 13:46 UTCEPSS rescore
  7. 2026-08-07 16:40 UTCEG score recompute
  8. 2026-08-06 18:06 UTCEG score recompute
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-05 19:34 UTCEG score recompute
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 20:06 UTCEG score recompute
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 19:04 UTCEG score recompute
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 08:29 UTCEG score recompute
  18. 2026-08-02 02:27 UTCEPSS rescore
  19. 2026-08-01 09:56 UTCEG score recompute
  20. 2026-08-01 04:16 UTCEPSS rescore
  21. 2026-07-30 23:39 UTCEG score recompute
  22. 2026-07-30 16:28 UTCEPSS rescore
  23. 2026-07-30 12:22 UTCEG score recompute
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-29 01:49 UTCEG score recompute
  26. 2026-07-28 15:37 UTCEPSS rescore
  27. 2026-07-28 01:02 UTCEG score recompute
  28. 2026-07-26 14:25 UTCEG score recompute
  29. 2026-07-24 14:18 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 03:18 UTCEG score recompute
  32. 2026-07-22 14:08 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-16 17:03 UTCEPSS rescore
  35. 2026-07-15 16:57 UTCEPSS rescore
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-13 22:30 UTCEPSS rescore
  38. 2026-07-13 06:13 UTCEPSS rescore
  39. 2026-07-12 05:46 UTCEPSS rescore
  40. 2026-07-11 08:27 UTCEPSS rescore
  41. 2026-07-09 19:10 UTCEPSS rescore
  42. 2026-07-08 15:16 UTCEPSS rescore
  43. 2026-07-07 13:46 UTCEPSS rescore
  44. 2026-07-05 02:30 UTCEPSS rescore
  45. 2026-07-04 06:31 UTCEPSS rescore
  46. 2026-07-01 15:07 UTCEPSS rescore
  47. 2026-06-30 23:22 UTCEPSS rescore
  48. 2026-06-30 04:51 UTCEG score recompute▲ 7.10
  49. 2026-06-29 14:06 UTCEPSS rescore
  50. 2026-06-29 14:06 UTCEPSS rescore
  51. 2026-06-29 13:32 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-27 09:36 UTCNVD update
  56. 2026-06-27 09:15 UTCEG score recompute
  57. 2026-06-27 09:14 UTCMITRE cvelistV5first tracked

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% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
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