Skip to content
Networks

CVE-2026-74287

9.1
Critical
EPSS 0.51%Patch availableAug 17, 2026

Linux SCTP parsing flaw allows out-of-bounds reads from crafted INIT/ASCONF packets.

common questions

Is CVE-2026-74287 being exploited?

Not confirmed. CVE-2026-74287 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.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-74287?

CVE-2026-74287 is rated Critical with a CVSS score of 9.1. 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-74287?

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

What does CVE-2026-74287 affect?

CVE-2026-74287 affects Linux kernel SCTP implementation (affected kernel versions prior to fix), Linux distributions using affected kernels (Debian/Ubuntu/RHEL/SUSE/etc.). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74287?

Apply vendor kernel patches or update to patched kernel ASAP

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

executive summary
technical analysis
affected
Linux kernel SCTP implementation (affected kernel versions prior to fix)Linux distributions using affected kernels (Debian/Ubuntu/RHEL/SUSE/etc.)
impact

Remote attacker can send malformed SCTP INIT/ASCONF to trigger out-of-bounds reads, causing info disclosure or kernel crash.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 06c8bf48505f2fef265931db82d5003d302a347b
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 28ba1d3c956604a89168adfb4c97cfc6c509bba5
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 3a44b2602d57e11e2eb85958d4cd500d14a27d9e
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 85f54cf589163a75fa06e37d8c2a4a72824c6dd1
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 92e4adfee56f32a963ebb105c6cd9a1ed707262a
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < ed8605c6f39b9b84f9a4631db6deb25e7f1e973c
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0
  • affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e9361d0ca55c4af12aac09e2572852fa91046229
  • affected2.6.12
vendor says fixed in< 2.6.12, >= 5.10.261 and <= 5.10.*, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

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