CVE-2026-52986

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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:

netfilter: nf_conntrack_sip: don't use simple_strtoul

Replace unsafe port parsing in epaddr_len(), ct_sip_parse_header_uri(), and ct_sip_parse_request() with a new sip_parse_port() helper that validates each digit against the buffer limit, eliminating the use of simple_strtoul() which assumes NUL-terminated strings.

The previous code dereferenced pointers without bounds checks after sip_parse_addr() and relied on simple_strtoul() on non-NUL-terminated skb data. A port that reaches the buffer limit without a trailing character is also rejected as malformed.

Also get rid of all simple_strtoul() usage in conntrack, prefer a stricter version instead. There are intentional changes:

  • Bail out if number is > UINT_MAX and indicate a failure, same for
too long sequences. While we do accept 05535 as port 5535, we will not accept e.g. 'sip:10.0.0.1:005060'. While its syntactically valid under RFC 3261, we should restrict this to not waste cycles when presented with malformed packets with 64k '0' characters.
  • Force base 10 in ct_sip_parse_numerical_param(). This is used to fetch
'expire=' and 'rports='; both are expected to use base-10.
  • In nf_nat_sip.c, only accept the parsed value if its within the 1k-64k
range.
  • epaddr_len now returns 0 if the port is invalid, as it already does
for invalid ip addresses. This is intentional. nf_conntrack_sip performs lots of guesswork to find the right parts of the message to parse. Being stricter could break existing setups. Connection tracking helpers are designed to allow traffic to pass, not to block it.

Based on an earlier patch from Jenny Guanni Qu .

CVSS v3
9.8
EG Score
9.8(high)
EPSS
42.5%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f69c323ae0ab517e595c2cc74e0ae0d9d085611
generic

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c6afcb1c3cbb2c0da65b8515ac14d7273872f84
generic

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8cf6809cddcbe301aedfc6b51bcd4944d45795f6
generic

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8cd0358379570003659186706e077929d6930c40
generic

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7df9863bf538a626e8a684e59cb2c43eac0ef3c8
generic

netfilter: nf_conntrack_sip: don't use simple_strtoul - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/523762e3b6933fff81f01dfa3c60c0774044cdab

Vendor Advisories for CVE-2026-52986(2)

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 89× in last 7d / 101× 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.

Showing the most recent 100 of 101 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-52986?
CVE-2026-52986 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nfconntracksip: don't use simple_strtoul Replace unsafe port parsing in epaddrlen(), ctsipparseheader_uri(), and ctsipparserequest() with a new sipparse_port() helper that validates each digit against the buffer limit,…
When was CVE-2026-52986 disclosed?
CVE-2026-52986 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52986 actively exploited?
CVE-2026-52986 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52986?
CVE-2026-52986 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-52986?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52986, 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-52986

Explore →

Is Your Infrastructure Affected by CVE-2026-52986?

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