← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-53266 exploited? Yes: in CISA KEV since 18 Sep 2026

Gociux · Linux Kernel · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-53266, Linux Kernel Out-of-Bounds Write Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 18 Sep 2026, 85 days after it was published. It affects Linux Kernel. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 18 Sep 2026
ransomwareNot knownno confirmed use
EPSSbelow top 10%lower predicted activity right now (it is still confirmed exploited)
severity8.8CVSS 3.1 · high
US federal due21 Sep 2026BOD 22-01 deadline

What it is

Linux Kernel contains an out-of-bounds write vulnerability in the ebtables SNAT target which allows an ARP sender hardware address rewrite to write directly into a nonlinear socket-buffer fragment backed by a splice-imported file page. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.

VendorLinux (32 exploited CVEs in KEV)
ProductKernel
VulnerabilityLinux Kernel Out-of-Bounds Write Vulnerability
WeaknessCWE-787
Published25 Jun 2026
Added to KEV18 Sep 2026
Reported by (CNA)Linux

What to do

  1. Check whether you run it. Look for Kernel in your asset inventory, including appliances and cloud images. Stack check lists every exploited Linux CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 25 Jun 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Linux.

Other exploited CVEs in Kernel

References

Questions

Is CVE-2026-53266 being exploited?

Yes. CISA added CVE-2026-53266 to the Known Exploited Vulnerabilities catalog on 18 Sep 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-53266 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-53266?

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. Check Linux's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Kernel and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in September 2026 · Linux scorecard · act-now radar.

Running Linux in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →