CVE-2026-49413

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
7.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (FreeBSD) lists FreeBSD versions 15.0-RELEASE up to but not including p10, 14.4-RELEASE up to but not including p6 and 14.3-RELEASE up to but not including p15 as affected. No release containing a fix is confirmed on record.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 27, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No fix on record yet.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 123 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 23 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-12 16:00 UTCEG score recompute
  4. 2026-10-11 19:43 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-09-23 07:40 UTCEG score recompute
  23. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-18 07:06 UTCEG score recompute
Show 75 more
  1. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-09-12 15:18 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-09-06 14:49 UTCEG score recompute
  9. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-08-30 19:11 UTCEG score recompute
  15. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-08-27 22:51 UTCEG score recompute
  18. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-08-24 21:46 UTCEG score recompute
  22. 2026-08-23 08:31 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  24. 2026-08-22 09:15 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  26. 2026-08-21 04:54 UTCEG score recompute
  27. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  28. 2026-08-20 06:04 UTCEG score recompute
  29. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  30. 2026-08-18 23:27 UTCEG score recompute
  31. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  32. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  33. 2026-08-17 02:11 UTCEG score recompute
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  35. 2026-08-16 03:39 UTCEG score recompute
  36. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  37. 2026-08-15 05:07 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  39. 2026-08-14 06:32 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  41. 2026-08-12 20:44 UTCEG score recompute
  42. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  43. 2026-08-11 22:12 UTCEG score recompute
  44. 2026-08-11 10:49 UTCEG score recompute
  45. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  46. 2026-08-10 01:00 UTCEG score recompute
  47. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  48. 2026-08-07 16:40 UTCEG score recompute
  49. 2026-08-06 18:06 UTCEG score recompute
  50. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  51. 2026-08-05 19:34 UTCEG score recompute
  52. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-04 20:06 UTCEG score recompute
  54. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  55. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  56. 2026-08-03 19:04 UTCEG score recompute
  57. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  58. 2026-08-02 08:29 UTCEG score recompute
  59. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-08-01 09:56 UTCEG score recompute
  61. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  62. 2026-07-30 23:39 UTCEG score recompute
  63. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  64. 2026-07-30 12:22 UTCEG score recompute
  65. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  66. 2026-07-29 01:49 UTCEG score recompute
  67. 2026-07-28 15:37 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  68. 2026-07-28 01:02 UTCEG score recompute
  69. 2026-07-26 14:25 UTCEG score recompute
  70. 2026-07-24 14:18 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  71. 2026-07-23 14:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  72. 2026-07-23 03:18 UTCEG score recompute
  73. 2026-07-22 14:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  74. 2026-07-20 17:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  75. 2026-07-16 17:03 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2026-49413?
CVE-2026-49413 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-49413 was made public on June 9, 2026: that is the date its CVE record's CNA, FreeBSD, gives for when the vulnerability was made public. The CVE record itself was published on June 27, 2026. EchelonGraph's copy of the record carries a last-modified date of July 1, 2026; the record at its source may have been updated since.
Is CVE-2026-49413 actively exploited?
CVE-2026-49413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-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?
No fix for CVE-2026-49413 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (FreeBSD) lists FreeBSD versions 15.0-RELEASE up to but not including p10, 14.4-RELEASE up to but not including p6 and 14.3-RELEASE up to but not including p15 as affected. No release containing a fix is confirmed on record.

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.