CVE-2026-53218

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: 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: nft_exthdr: fix register tracking for F_PRESENT flag

nft_exthdr_init() passes user-controlled priv->len to nft_parse_register_store(), which marks that many bytes in the register bitmap as initialized. However, when NFT_EXTHDR_F_PRESENT is set, the eval paths write only 1 byte (nft_reg_store8) or 4 bytes (*dest = 0 on TCP/DCCP error path). When len > 4, registers beyond the first are never written, retaining uninitialized stack data from nft_regs.

Bail out if userspace requests too much data when F_PRESENT is set.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
2.4%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (8)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8738b1b6d0e639ca1fc0f61516afd3557ac4ecc6
generic

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78069a6d8bc86c9e036eb82c2af4a19cc1871a53
generic

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/772cecf198da732faebb5dcfc46d66a505be8495
generic

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67b27434c43b68a97becda98c9f0c8cf6cba2134
generic

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46fc15a044e9938e7ea77786fb37edd2cd74f031
generic

netfilter: nft_exthdr: fix register tracking for F_PRESENT flag - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19748967d59c31d24d21d40b728570788310b237

Vendor Advisories for CVE-2026-53218(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 74× 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-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 20:04 UTCVendor advisory
  12. 2026-07-16 20:04 UTCGHSA enrichment
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-15 19:25 UTCVendor advisory
  15. 2026-07-15 19:25 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 19:46 UTCVendor advisory
  21. 2026-07-14 19:46 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 20:06 UTCGHSA enrichment
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 49 more
  1. 2026-07-12 20:27 UTCVendor advisory
  2. 2026-07-12 20:27 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 20:48 UTCVendor advisory
  5. 2026-07-11 20:48 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 21:09 UTCVendor advisory
  9. 2026-07-10 21:09 UTCGHSA enrichment
  10. 2026-07-09 21:30 UTCVendor advisory
  11. 2026-07-09 21:30 UTCGHSA enrichment
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 21:50 UTCVendor advisory
  15. 2026-07-08 21:50 UTCGHSA enrichment
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-07 22:11 UTCVendor advisory
  19. 2026-07-07 22:11 UTCGHSA enrichment
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 22:32 UTCVendor advisory
  23. 2026-07-06 22:32 UTCGHSA enrichment
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 02:23 UTCEPSS rescore
  27. 2026-07-06 02:23 UTCEPSS rescore
  28. 2026-07-05 22:53 UTCVendor advisory
  29. 2026-07-05 22:53 UTCGHSA enrichment
  30. 2026-07-04 23:13 UTCEG score recompute▲ 5.50
  31. 2026-07-04 23:13 UTCVendor advisory
  32. 2026-07-04 23:13 UTCGHSA enrichment
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-04 06:31 UTCEPSS rescore
  35. 2026-07-02 22:05 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  36. 2026-07-01 18:51 UTCVendor advisory
  37. 2026-07-01 18:51 UTCGHSA enrichment
  38. 2026-07-01 15:07 UTCEPSS rescore
  39. 2026-06-29 14:06 UTCEPSS rescore
  40. 2026-06-29 14:06 UTCEPSS rescore
  41. 2026-06-28 14:29 UTCVendor advisory
  42. 2026-06-28 14:29 UTCGHSA enrichment
  43. 2026-06-28 14:07 UTCEPSS rescore
  44. 2026-06-28 04:56 UTCEPSS rescore
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-27 03:08 UTCEPSS rescore
  47. 2026-06-25 13:49 UTCEPSS rescore
  48. 2026-06-25 10:07 UTCEG score recompute
  49. 2026-06-25 10:07 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53218?
CVE-2026-53218 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nftexthdr: fix register tracking for FPRESENT flag nftexthdrinit() passes user-controlled priv->len to nftparseregister_store(), which marks that many bytes in the register bitmap as initialized. However, when…
When was CVE-2026-53218 disclosed?
CVE-2026-53218 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53218 actively exploited?
CVE-2026-53218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53218?
CVE-2026-53218 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53218, 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-53218

Explore →

Is Your Infrastructure Affected by CVE-2026-53218?

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

Start Free Scan →Browse All CVEs