CVE-2026-72419

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.2%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: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init()

We ran into below KASAN splat, which is mostly uninteresting, beside for having nf_nat_register_fn() in the call chain as a cause for the offending access:

================================================================== BUG: KASAN: slab-out-of-bounds in nf_nat_register_fn+0x5f9/0x640 Read of size 8 at addr ffff890031e54c20 by task iptables/9510

CPU: 0 UID: 0 PID: 9510 Comm: iptables Not tainted 6.18.18-grsec-full-20260320181326 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: […] dump_stack_lvl+0xee/0x160 ffff88004117eeb8 […] print_report+0x6e/0x640 ffff88004117eee0 […] ? __phys_addr+0x8e/0x140 ffff88004117eef0 […] ? kasan_addr_to_slab+0x51/0xe0 ffff88004117ef08 […] ? complete_report_info+0xec/0x1c0 ffff88004117ef20 […] ? nf_nat_register_fn+0x5f9/0x640 ffff88004117ef48 […] kasan_report+0xbc/0x140 ffff88004117ef50 […] ? nf_nat_register_fn+0x5f9/0x640 ffff88004117ef90 […] nf_nat_register_fn+0x5f9/0x640 ffff88004117eff8 […] ? nf_nat_icmp_reply_translation+0x6e0/0x6e0 ffff88004117f070 […] nf_tables_register_hook.part.0+0xa0/0x220 ffff88004117f080 […] nf_tables_addchain.constprop.0+0x1054/0x1fc0 ffff88004117f0b8 […] ? nft_chain_lookup.part.0+0x4ce/0xac0 ffff88004117f130 […] ? nf_tables_abort+0x3d80/0x3d80 ffff88004117f190 […] ? nf_tables_dumpreset_obj+0x100/0x100 ffff88004117f1c8 […] ? nft_table_lookup.part.0+0x255/0x300 ffff88004117f310 […] ? nf_tables_newchain+0x21a4/0x2fa0 ffff88004117f358 […] nf_tables_newchain+0x21a4/0x2fa0 ffff88004117f360 […] ? nf_tables_addchain.constprop.0+0x1fc0/0x1fc0 ffff88004117f458 […] ? nla_get_range_signed+0x4a0/0x4a0 ffff88004117f488 […] ? lock_acquire+0x16f/0x320 ffff88004117f490 […] ? find_held_lock+0x3b/0xe0 ffff88004117f4b0 […] ? __nla_parse+0x45/0x80 ffff88004117f500 […] nfnetlink_rcv_batch+0xbca/0x19a0 ffff88004117f550 […] ? nfnetlink_net_exit_batch+0x120/0x120 ffff88004117f618 […] ? __sanitizer_cov_trace_switch+0x63/0xe0 ffff88004117f720 […] ? gr_acl_handle_mmap+0x1c4/0x320 ffff88004117f7c0 […] ? nla_get_range_signed+0x4a0/0x4a0 ffff88004117f7e8 […] ? gr_is_capable+0x6f/0xe0 ffff88004117f830 […] ? __nla_parse+0x45/0x80 ffff88004117f860 […] ? skb_pull+0x103/0x1a0 ffff88004117f880 […] nfnetlink_rcv+0x3db/0x4a0 ffff88004117f8b0 […] ? nfnetlink_rcv_batch+0x19a0/0x19a0 ffff88004117f8d8 […] ? netlink_lookup+0xe2/0x240 ffff88004117f900 […] netlink_unicast+0x74b/0xb00 ffff88004117f930 […] ? netlink_attachskb+0xb20/0xb20 ffff88004117f980 […] ? __check_object_size+0x3e/0xaa0 ffff88004117f998 […] ? security_netlink_send+0x51/0x160 ffff88004117f9c8 […] netlink_sendmsg+0xa03/0x1200 ffff88004117f9f8 […] ? netlink_unicast+0xb00/0xb00 ffff88004117fa70 […] ? netlink_unicast+0xb00/0xb00 ffff88004117fac8 […] ? ____sys_sendmsg+0xe2a/0x1040 ffff88004117faf8 […] ____sys_sendmsg+0xe2a/0x1040 ffff88004117fb00 […] ? kernel_recvmsg+0x300/0x300 ffff88004117fb60 […] ? reacquire_held_locks+0xe9/0x260 ffff88004117fbc8 […] ___sys_sendmsg+0x138/0x200 ffff88004117fbf8 […] ? do_recvmmsg+0x7e0/0x7e0 ffff88004117fc30 […] ? lockdep_hardirqs_on_prepare+0x101/0x1e0 ffff88004117fc50 […] ? lock_acquire+0x16f/0x320 ffff88004117fd20 […] ? lock_acquire+0x16f/0x320 ffff88004117fd58 […] ? find_held_lock+0x3b/0xe0 ffff88004117fd70 […] __sys_sendmsg+0x17a/0x260 ffff88004117fdc8 […] ? __sys_sendmsg_sock+0x80/0x80 ffff88004117fdf0 […] ? syscall_trace_enter+0x15e/0x2c0 ffff88004117fe98 […] do_syscall_64+0x7d/0x400 ffff88004117fec8 […] entry_SYSCALL_64_safe_stack+0x4a/0x60 ffff88004117fef8 ==================================================================

The out-of-bounds report, though, is a red herring as it is f ---truncated---

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.2% × 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.2%
EPSS %ILE
6th
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.2% 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 (6)

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

netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87f7a720de2545fdac29c85acb7163676feacdaf
Web page

netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/359d8ff97362a4662356104540e4814bff9dad7c
Web page

netfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/069cfe3de2a5e16069485893cd04665ab769c1d8

Vendor Advisories for CVE-2026-72419(1)

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 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
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
—

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 77× 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 99 of 222 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 123 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.2% · 6th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-18 03:16 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-16 19:40 UTCEG score recompute
  6. 2026-10-16 19:40 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-16 19:02 UTCEG score recompute
  8. 2026-10-16 19:01 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-13 08:14 UTCEG score recompute
  14. 2026-10-13 08:14 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-12 15:41 UTCEG score recompute
  17. 2026-10-11 19:27 UTCEG score recompute
  18. 2026-10-11 16:43 UTCEG score recompute
  19. 2026-10-11 14:03 UTCEG score recompute
  20. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-09 20:07 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:37 UTCEG score recompute
Show 74 more
  1. 2026-10-06 22:37 UTCVendor advisory
  2. 2026-10-06 22:37 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-06 09:13 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-05 20:39 UTCEG score recompute
  6. 2026-10-05 20:39 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-05 09:41 UTCEG score recompute
  9. 2026-10-05 09:41 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-04 22:01 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-04 06:32 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-03 19:34 UTCEG score recompute
  14. 2026-10-03 19:34 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-02 18:22 UTCEG score recompute
  17. 2026-10-02 18:22 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-02 07:10 UTCEG score recompute
  19. 2026-10-02 07:09 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-01 08:04 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-09-30 21:06 UTCEG score recompute
  23. 2026-09-30 21:06 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-29 00:07 UTCEG score recompute
  26. 2026-09-29 00:07 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  27. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-28 06:31 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-09-27 19:33 UTCEG score recompute
  30. 2026-09-27 19:33 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-27 08:36 UTCEG score recompute
  33. 2026-09-27 08:36 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-25 02:39 UTCEG score recompute
  36. 2026-09-25 02:39 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-09-24 08:02 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-09-23 20:35 UTCEG score recompute
  39. 2026-09-23 20:35 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-09-23 07:46 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-09-22 20:49 UTCEG score recompute
  43. 2026-09-22 20:49 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-09-22 07:09 UTCEG score recompute
  45. 2026-09-22 07:09 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-09-21 20:11 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-09-21 09:13 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-09-20 20:56 UTCEG score recompute
  50. 2026-09-20 20:56 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-09-20 09:59 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-09-19 23:01 UTCEG score recompute
  54. 2026-09-19 23:01 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-19 11:05 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-09-18 22:00 UTCEG score recompute
  57. 2026-09-18 22:00 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-09-18 09:10 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-09-17 22:12 UTCEG score recompute
  61. 2026-09-17 22:12 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-17 11:13 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-09-16 23:37 UTCEG score recompute
  64. 2026-09-16 23:37 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  66. 2026-09-16 06:20 UTCEG score recompute
  67. 2026-09-16 06:20 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-09-15 19:22 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-15 07:11 UTCEG score recompute
  71. 2026-09-15 07:11 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  73. 2026-09-14 20:13 UTCGHSA enrichmentGHSA-mpg4-7mw3-ccvq · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-09-14 07:28 UTCEG score recompute

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-72419?
CVE-2026-72419 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: nfnat: avoid invalid natnet pointer use on failed nfnatinit() We ran into below KASAN splat, which is mostly uninteresting, beside for having nfnatregister_fn() in the call chain as a cause for the offending access:…
When was the CVE record for CVE-2026-72419 published?
The CVE record for CVE-2026-72419 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-72419 actively exploited?
CVE-2026-72419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72419?
CVE-2026-72419 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-72419?
A fix for CVE-2026-72419 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72419 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-72419

Explore →

Is Your Infrastructure Affected by CVE-2026-72419?

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

Book a Demo →Browse All CVEs