CVE-2026-53109

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-38977 (ENISA EUVD) · GHSA-r4jc-xrhv-v4rj (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:

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy

powerpc uses pt_frag_refcount as a reference counter for tracking it's pte and pmd page table fragments. For PTE table, in case of Hash with 64K pagesize, we have 16 fragments of 4K size in one 64K page.

Patch series [1] "mm: free retracted page table by RCU" added pte_free_defer() to defer the freeing of PTE tables when retract_page_tables() is called for madvise MADV_COLLAPSE on shmem range. [1]: https://lore.kernel.org/all/[email protected]/

pte_free_defer() sets the active flag on the corresponding fragment's folio & calls pte_fragment_free(), which reduces the pt_frag_refcount. When pt_frag_refcount reaches 0 (no active fragment using the folio), it checks if the folio active flag is set, if set, it calls call_rcu to free the folio, it the active flag is unset then it calls pte_free_now().

Now, this can lead to following problem in a corner case...

[ 265.351553][ T183] BUG: Bad page state in process a.out pfn:20d62 [ 265.353555][ T183] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x20d62 [ 265.355457][ T183] flags: 0x3ffff800000100(active|node=0|zone=0|lastcpupid=0x7ffff) [ 265.358719][ T183] raw: 003ffff800000100 0000000000000000 5deadbeef0000122 0000000000000000 [ 265.360177][ T183] raw: 0000000000000000 c0000000119caf58 00000000ffffffff 0000000000000000 [ 265.361438][ T183] page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set [ 265.362572][ T183] Modules linked in: [ 265.364622][ T183] CPU: 0 UID: 0 PID: 183 Comm: a.out Not tainted 6.18.0-rc3-00141-g1ddeaaace7ff-dirty #53 VOLUNTARY [ 265.364785][ T183] Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected) 0x801200 0xf000006 of:SLOF,git-ee03ae pSeries [ 265.364908][ T183] Call Trace: [ 265.364955][ T183] [c000000011e6f7c0] [c000000001cfaa18] dump_stack_lvl+0x130/0x148 (unreliable) [ 265.365202][ T183] [c000000011e6f7f0] [c000000000794758] bad_page+0xb4/0x1c8 [ 265.365384][ T183] [c000000011e6f890] [c00000000079c020] __free_frozen_pages+0x838/0xd08 [ 265.365554][ T183] [c000000011e6f980] [c0000000000a70ac] pte_frag_destroy+0x298/0x310 [ 265.365729][ T183] [c000000011e6fa30] [c0000000000aa764] arch_exit_mmap+0x34/0x218 [ 265.365912][ T183] [c000000011e6fa80] [c000000000751698] exit_mmap+0xb8/0x820 [ 265.366080][ T183] [c000000011e6fc30] [c0000000001b1258] __mmput+0x98/0x300 [ 265.366244][ T183] [c000000011e6fc80] [c0000000001c81f8] do_exit+0x470/0x1508 [ 265.366421][ T183] [c000000011e6fd70] [c0000000001c95e4] do_group_exit+0x88/0x148 [ 265.366602][ T183] [c000000011e6fdc0] [c0000000001c96ec] pid_child_should_wake+0x0/0x178 [ 265.366780][ T183] [c000000011e6fdf0] [c00000000003a270] system_call_exception+0x1b0/0x4e0 [ 265.366958][ T183] [c000000011e6fe50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec

The bad page state error occurs when such a folio gets freed (with active flag set), from do_exit() path in parallel.

... this can happen when the pte fragment was allocated from this folio, but when all the fragments get freed, the pte_frag_refcount still had some unused fragments. Now, if this process exits, with such folio as it's cached pte_frag in mm->context, then during pte_frag_destroy(), we simply call pagetable_dtor() and pagetable_free(), meaning it doesn't clear the active flag. This, can lead to the above bug. Since we are anyway in do_exit() path, then if the refcount is 0, then I guess it should be ok to simply clear the folio active flag before calling pagetable_dtor() & pagetable_free().

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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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-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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 24, 2026

Last Modified

November 6, 2026

Advisory Details (3)

Auto-updated Jul 23, 2026
Patch available.
Web page

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a32db6fca3c74b4eb8bae5470f0680deb4cbac6f

Vendor Advisories for CVE-2026-53109(2)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-28ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-28ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-28ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-28ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-28ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-28ubuntu
linuxKernel @ 6.18.33 (fixes >=6.6.0)—osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (144 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

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 9× in last 7d / 42× 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 332 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 232 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53109?
CVE-2026-53109 is a high-severity vulnerability; its CVE record was published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy powerpc uses pt_frag_refcount as a reference counter for tracking it's pte and pmd page table fragments. For PTE table, in case of Hash with 64K pagesize, we have 16…
When was the CVE record for CVE-2026-53109 published?
The CVE record for CVE-2026-53109 was published on June 24, 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-53109 actively exploited?
CVE-2026-53109 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-53109?
CVE-2026-53109 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53109?
A fix for CVE-2026-53109 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53109 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-53109

Explore →

Is Your Infrastructure Affected by CVE-2026-53109?

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

Book a Demo →Browse All CVEs