Exploited CVEs / Linux / CVE-2026-53362

CVE-2026-53362

Linux Kernel Unspecified Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-08-30 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

HighCISA KEV
7.8
CVSS v3 base
<1%
EPSS exploit probability
High
Severity
2026-08-27
Added to KEV
2026-08-30 (past due)
CISA due date

Actively exploited Linux Kernel vulnerability, High severity, CVSS v3 7.8. Added to the CISA KEV catalog 2026-08-27.

Senserva AI read on CVE-2026-53362CISA required actionOfficial fix for CVE-2026-53362Admin questions#23 hottest CVE right now

Senserva AI Opinion for CVE-2026-53362

This is a High severity kernel flaw (CVSS 7.3) in the IPv6 stack of azl3 kernel 6.6.143.1-1 on Azure Linux 3.0, tied to mishandling of the fragment gap on the paged allocation path when building fragmented IPv6 packets. Any Azure Linux 3.0 host running this kernel and processing IPv6 traffic is exposed, which typically means containers and VM workloads that have not pinned to an older kernel. It is not in CISA KEV and has no known ransomware use, so this is a patch-on-schedule item rather than an emergency.

Do this: Update the azl3 kernel past 6.6.143.1-1 on all Azure Linux 3.0 hosts and reboot to load the fixed kernel.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-53362

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-08-30; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated September 3, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-53362

Published
2026-07-05
Last revised
2026-07-08
Changes tracked
2

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

CISA confirmed active exploitation of CVE-2026-53362 on 2026-08-27.

0%25%50%75%100%CISA KEVCISA KEV on 2026-08-272026-08-27: EPSS 0.3%2026-08-27: EPSS 0.3%2026-08-29: EPSS 0.5%2026-08-29: EPSS 0.5%EPSS 0.5%2026-08-272026-08-29

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-07-17 CVSS 7.3 to 0.0
  • 2026-08-27 CVSS 0.0 to 7.3; CVSS 7.3 to 7.8; EPSS first scored at 0.3%; added to the CISA KEV catalog by CISA
  • 2026-08-29 EPSS 0.3% to 0.5%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-08-30 (past due).

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Official fix for CVE-2026-53362

Check the vendor's security advisory channel for the patched Kernel versions and workarounds.

Common questions about CVE-2026-53362

Is CVE-2026-53362 actively exploited?

Yes. CVE-2026-53362 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-08-27, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.

What is the CISA deadline and required action for CVE-2026-53362?

CISA set the federal (BOD 22-01) remediation due date at 2026-08-30, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What fixes CVE-2026-53362?

Check the vendor's security advisory for the patched Kernel versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-53362?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-53362's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed once a day (early morning US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.