CVE-2026-74287

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

sctp: validate embedded address parameter length

sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP, and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer parameter is large enough to contain an embedded address parameter header, but does not verify that the embedded address parameter's declared length fits within the bounds of the outer parameter.

Later, sctp_process_param() and sctp_process_asconf_param() extract the embedded address parameter and pass it to af->from_addr_param(), which uses the address parameter length to parse the variable-length address payload. A malformed peer can therefore advertise an embedded address parameter length that exceeds the remaining bytes in the enclosing parameter.

Validate that addr_param->p.length does not exceed the space available after the sctp_addip_param header before processing the embedded address parameter. Reject malformed parameters when the embedded address length extends beyond the enclosing parameter bounds.

This prevents out-of-bounds reads when parsing malformed parameters carried in INIT or ASCONF processing paths.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed8605c6f39b9b84f9a4631db6deb25e7f1e973c
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e9361d0ca55c4af12aac09e2572852fa91046229
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92e4adfee56f32a963ebb105c6cd9a1ed707262a
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85f54cf589163a75fa06e37d8c2a4a72824c6dd1
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a44b2602d57e11e2eb85958d4cd500d14a27d9e
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28ba1d3c956604a89168adfb4c97cfc6c509bba5
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0
generic

sctp: validate embedded address parameter length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06c8bf48505f2fef265931db82d5003d302a347b

Vendor Advisories for CVE-2026-74287(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 47× in last 7d / 47× 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-21 05:12 UTCGHSA enrichment
  2. 2026-08-21 01:06 UTCEG score recompute
  3. 2026-08-21 01:06 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 20:59 UTCGHSA enrichment
  6. 2026-08-20 16:53 UTCGHSA enrichment
  7. 2026-08-20 12:47 UTCGHSA enrichment
  8. 2026-08-20 08:41 UTCGHSA enrichment
  9. 2026-08-20 04:36 UTCGHSA enrichment
  10. 2026-08-20 00:30 UTCGHSA enrichment
  11. 2026-08-19 20:24 UTCEG score recompute
  12. 2026-08-19 20:24 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 16:16 UTCGHSA enrichment
  15. 2026-08-19 12:06 UTCGHSA enrichment
  16. 2026-08-19 08:00 UTCGHSA enrichment
  17. 2026-08-19 03:54 UTCGHSA enrichment
  18. 2026-08-18 23:48 UTCGHSA enrichment
  19. 2026-08-18 19:41 UTCGHSA enrichment
  20. 2026-08-18 15:35 UTCEG score recompute
  21. 2026-08-18 15:35 UTCGHSA enrichment
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 11:25 UTCGHSA enrichment
  25. 2026-08-18 07:19 UTCGHSA enrichment
Show 22 more
  1. 2026-08-18 03:13 UTCGHSA enrichment
  2. 2026-08-17 23:06 UTCGHSA enrichment
  3. 2026-08-17 18:58 UTCGHSA enrichment
  4. 2026-08-17 14:35 UTCEG score recompute
  5. 2026-08-17 14:35 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:28 UTCEG score recompute
  8. 2026-08-17 10:28 UTCGHSA enrichment
  9. 2026-08-17 06:22 UTCEG score recompute
  10. 2026-08-17 06:22 UTCGHSA enrichment
  11. 2026-08-17 05:56 UTCEG score recompute 9.10
  12. 2026-08-17 05:56 UTCGHSA enrichment
  13. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  14. 2026-08-17 05:27 UTCEG score recompute
  15. 2026-08-17 05:27 UTCGHSA enrichment
  16. 2026-08-17 05:25 UTCMITRE cvelistV5
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:15 UTCEPSS rescore
  20. 2026-08-15 06:23 UTCNVD update
  21. 2026-08-15 06:16 UTCEG score recompute
  22. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74287?
CVE-2026-74287 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: validate embedded address parameter length sctpverifyasconf() and sctpverifyparam() only validate ADDIP, DELIP, and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct sctpaddipparam) + sizeof(struct…
When was CVE-2026-74287 disclosed?
CVE-2026-74287 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74287 actively exploited?
CVE-2026-74287 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74287?
CVE-2026-74287 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-74287?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74287, 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-74287

Explore →

Is Your Infrastructure Affected by CVE-2026-74287?

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