Skip to content
Systems

CVE-2026-49415

8.8
High
EPSS 0.22%Patch availableAug 21, 2026

Local kernel race in execve allows privilege escalation via /proc.

common questions

Is CVE-2026-49415 being exploited?

Not confirmed. CVE-2026-49415 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.

How severe is CVE-2026-49415?

CVE-2026-49415 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49415?

Yes. A fix has been recorded for CVE-2026-49415. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49415 affect?

CVE-2026-49415 affects Linux kernel (execve path), Distributions exposing /proc or linprocfs, SUID/setuid binaries, Multi-user Linux systems. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49415?

Apply vendor kernel updates when released; restrict /proc (hidepid=2); remove untrusted SUID binaries.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (execve path)Distributions exposing /proc or linprocfsSUID/setuid binariesMulti-user Linux systems
impact

Local privilege escalation to root by modifying a SUID process's address space via a procfs race during execve.

action required

Immediate action required

affected versions
FreeBSD FreeBSD
  • affected>= 15.1-RELEASE and < p1
  • affected>= 15.0-RELEASE and < p11
  • affected>= 14.4-RELEASE and < p7
  • affected>= 14.3-RELEASE and < p16

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free