CVE-2026-53267

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-06-25. 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

Also known asEUVD-2026-39218 (ENISA EUVD) · GHSA-mrf2-hc9c-229v (GitHub Security Advisories)Source: ENISA EUVD

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: nft_ct: bail out on template ct in get eval

I noticed this issue while looking at a historic syzbot report [1].

A rule like the one below is enough to trigger the bug:

table ip t { chain pre { type filter hook prerouting priority raw; ct zone set 1 ct original saddr 1.2.3.4 accept } }

The first expression attaches a per-cpu template ct via nft_ct_set_zone_eval() (nf_ct_tmpl_alloc -> kzalloc, tuple is all zero, nf_ct_l3num(ct) == 0). The next expression then calls nft_ct_get_eval() on the same skb, treats the template as a real ct and hits the 16-byte memcpy path. With dreg at NFT_REG32_15 this overflows past struct nft_regs on the kernel stack; with smaller dreg values it silently clobbers adjacent registers.

Reject template ct at the eval entry and in nft_ct_get_fast_eval(), mirroring the check nft_ct_set_eval() already has. Additionally, bound the address copy in NFT_CT_SRC / NFT_CT_DST by priv->len instead of by nf_ct_l3num(ct): nf_ct_get_tuple() zeroes the tuple before pkt_to_tuple() fills in only the protocol-relevant leading bytes, so the trailing bytes of tuple->{src,dst}.u3.all are well-defined zero. priv->len is validated at rule load, so the copy size is now bounded by the destination register rather than by an untrusted field on the conntrack.

[1]: https://syzkaller.appspot.com/bug?id=389cf09cb72926114fce90dc85a2c3231dcb647c

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
1st
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-11-12). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

June 25, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Jun 28, 2026
Patch available.
Web page

netfilter: nft_ct: bail out on template ct in get eval - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f071b0bf078146368d18e4eec386bf2ddc0ab7e0
Web page

netfilter: nft_ct: bail out on template ct in get eval - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/af80f78ce984649e1698b841cd33f4fa505ad828
Web page

netfilter: nft_ct: bail out on template ct in get eval - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8470f676eadeab99132708acb1a85915664d6115
Web page

netfilter: nft_ct: bail out on template ct in get eval - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3027ecbdb5fdf9200251c21d4818e4c447ef78e1
Web page

netfilter: nft_ct: bail out on template ct in get eval - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e154b5f53f1b0b490c7b8b02499f90feb86b1d5

Vendor Advisories for CVE-2026-53267(2)

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

Patch Availability(19)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (371 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (147 versions)
  • every version up to 7.0.13-1: fixed in 7.0.13-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 378 rows 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 278 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53267?
CVE-2026-53267 is a high-severity vulnerability; its CVE record was published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_ct: bail out on template ct in get eval I noticed this issue while looking at a historic syzbot report [1]. A rule like the one below is enough to trigger the bug: table ip t { chain pre { type filter hook prerouting…
When was the CVE record for CVE-2026-53267 published?
The CVE record for CVE-2026-53267 was published on June 25, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-53267 actively exploited?
CVE-2026-53267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53267?
CVE-2026-53267 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-53267?
A fix for CVE-2026-53267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53267 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-53267

Explore →

Is Your Infrastructure Affected by CVE-2026-53267?

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