CVE-2026-74347

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate 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.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount

Add a refcount for struct nf_ct_timeout which is used by ct extension to set the custom ct timeout policy, this tells us that the ct timeout is being used by a conntrack entry. When the last conntrack entry drops the refcount on the ct timeout, the ct timeout is released.

Remove the refcount for control plane which controls if the ruleset refers to the timeout policy. After this update, it is possible to remove the ct timeout policy from nfnetlink_cttimeout immediately. This is for simplicity not to handle two refcounts on a single object.

Remove nf_queue_nf_hook_drop(): a packet sitting in nfqueue will just hold a reference to the nf_ct_timeout object until packet is reinjected, since this is part of the ct extension, this will be released by the time the conntrack is freed.

nf_ct_untimeout() is still called to clean up in a best effort basis: the ct timeout on existing entries gets removed when the ct timeout goes away, but as long as the iptables ruleset still refers to the ct timeout through a template, new conntracks may keep attaching it and extend its lifetime until the rule is removed.

nf_ct_untimeout() is not called anymore from module removal path, this is unlikely to find timeouts give module refcount is bumped, and the new refcount already tracks the ct timeout policy use so it is released when unused.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

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

August 15, 2026

Last Modified

October 16, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available.
Web page

netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9aeb0dcfeb460d33d61d434148b51103ab1d2013
Web page

netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d6a9cdb8d3a51d9cfe546a09a518ab3d2671549

Vendor Advisories for CVE-2026-74347(2)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-06ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-06ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-06ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 101× 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 245 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 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-74347?
CVE-2026-74347 is a high-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount Add a refcount for struct nfcttimeout which is used by ct extension to set the custom ct timeout policy, this tells us that the ct timeout is being used…
When was the CVE record for CVE-2026-74347 published?
The CVE record for CVE-2026-74347 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-74347 actively exploited?
CVE-2026-74347 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-74347?
CVE-2026-74347 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74347?
A fix for CVE-2026-74347 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74347 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74347

Explore →

Is Your Infrastructure Affected by CVE-2026-74347?

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