Linux Kernel Unspecified Vulnerability (CVE-2026-53362)
Published Last modified In CISA KEV since Sources: Ubuntu, CVE.org, Msrc Update Guide, Red Hat, pwn.watch, SUSE, Siemens ProductCERT, Debian, Debian LTS, BSI
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero.
The vulnerability is being actively exploited; treat it as a priority. Update Linux Kernel to version 6.1.177, Linux Kernel to version 6.6.144, Linux Kernel to version 6.12.95. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- Linux Kernel
lt 6.0..6.1.177 - Linux Kernel
lt 6.2..6.6.144 - Linux Kernel
lt 6.7..6.12.95 - Linux Kernel
lt 6.13..6.18.38 - Linux Kernel
lt 6.19..7.1.3
- Linux Kernel
- Fixed in
- Linux Kernel
6.1.177 - Linux Kernel
6.6.144 - Linux Kernel
6.12.95 - Linux Kernel
6.18.38 - Linux Kernel
7.1.3 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: Ubuntu, CVE.org, Msrc Update Guide, Red Hat, pwn.watch, SUSE, Siemens ProductCERT, Debian, Debian LTS, BSI
0.7 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 53.4
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 181.86 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.7 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 53.4
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 28 August 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-122
Response and mitigation
Why act now?
Prioritisation rationale
The flaw sits in the kernel's IPv6 networking subsystem and lets an unprivileged local user turn a UDPv6 socket with MSG_MORE plus MSG_SPLICE_PAGES into a heap corruption (overflow into skb_shared_info) — a textbook local-privilege-escalation primitive, which is why CISA added it to KEV. The attack vector is local, requires no user interaction and runs with low privileges, making it critical for shared hosts, container platforms, build infrastructure and anything that executes untrusted code or hosts many interactive users. Mass exploitation is not currently observed and there is no known ransomware tie-in, but the bug is a strong post-exploitation building block after an initial RCE and should be closed within the normal monthly patch cycle at elevated priority for NIS2-scope environments — faster on multi-tenant systems.
Runbook step 1
Immediate response (0-24 h)
- Deploy the kernel patch: upgrade affected branches to 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3 or 7.2. Pull distribution packages (SUSE, Red Hat, Ubuntu, Debian) from the respective vendor advisory and verify with
uname -rplusrpm -q kernelordpkg -l linux-image-*. - Schedule reboot windows for all Linux hosts with an active IPv6 stack; drive change tickets off
needs-restarting -ror/var/run/reboot-required. Evaluate live-patching (kpatch, kGraft, Ksplice) if downtime is costly — vendor availability per advisory. - As a stopgap, disable IPv6 on hosts that do not need it:
sysctl -w net.ipv6.conf.all.disable_ipv6=1andnet.ipv6.conf.default.disable_ipv6=1, persisted in/etc/sysctl.d/. Especially relevant for multi-tenant hosts, container workers and shared-shell systems. - Prioritise by attack surface: systems with locally-logged-in unprivileged users (jump hosts, build runners, Kubernetes workers running user workloads, HPC, shared dev VMs) first, then servers with broad SSH access.
- Restrict unprivileged user namespaces temporarily (
sysctl kernel.unprivileged_userns_clone=0oruser.max_user_namespaces=0) to shrink the exploit primitives available via UDPv6 sockets inside isolated namespaces.
- Deploy the kernel patch: upgrade affected branches to 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3 or 7.2. Pull distribution packages (SUSE, Red Hat, Ubuntu, Debian) from the respective vendor advisory and verify with
Runbook step 2
Mitigation layers
- Network segmentation: constrain IPv6 traffic in management and server VLANs via firewall or
ip6tablesto required flows only. Exploitation is local and does not need external reachability, but reducing IPv6 usage lowers accidental trigger risk. - Multi-tenant host hardening: enforce seccomp profiles for containers (Docker, Podman, containerd) that restrict
sendmsg/sendmmsgon AF_INET6 with MSG_SPLICE_PAGES and MSG_MORE. Docker's default seccomp profile partially covers this — audit custom profiles. - Kubernetes: enforce
allowPrivilegeEscalation: false,runAsNonRoot: trueand the PodSecurity "restricted" standard. Run pods without IPv6 need withhostNetwork: falseand configure the CNI so IPv6 is only enabled on demand. - IAM / least privilege: audit local shell access on jump hosts and build runners, remove dormant accounts, tighten
AllowUsers/AllowGroupsin sshd_config. Every removed local account directly shrinks the exploit surface. - Kernel hardening: set
kernel.dmesg_restrict=1,kernel.kptr_restrict=2,kernel.yama.ptrace_scope=2to make follow-up work for a heap overflow exploit (info leaks, debugging) harder. - Roll out EDR/AV with Linux kernel-exploit detection modules (Falco, Tracee, CrowdStrike, SentinelOne) on Linux workloads if not already present.
- Network segmentation: constrain IPv6 traffic in management and server VLANs via firewall or
Runbook step 3
Detection rules
- Falco/Tracee rule on unusual
sendmsgsyscalls combining MSG_SPLICE_PAGES (0x8000000) and MSG_MORE (0x8000) on AF_INET6 UDP sockets from unprivileged UIDs. Baseline first, then alert. - auditd rule:
-a always,exit -F arch=b64 -S socket -F a0=10 -F a1&2 -k ipv6_udp_socket(AF_INET6 = 10, SOCK_DGRAM = 2), correlated withexecveof unusual binaries from/tmp,/dev/shm, home directories. - Kernel oops / slab corruption in
dmesgand/var/log/kern.log: patterns such as "BUG: KASAN", "general protection fault", "slab-out-of-bounds", "corrupted skb_shared_info", stack traces including__ip6_append_data,ip6_append_data,udpv6_sendmsg. Sigma shape:detection: selection: Image: '/var/log/kern.log' Message|contains: - '__ip6_append_data' - 'skb_shared_info' - 'slab-out-of-bounds' - KQL for Defender for Endpoint / Sentinel on Linux telemetry:
DeviceEvents | where ActionType == "KernelOops" or AdditionalFields has "ip6_append_data" - EDR process ancestry: shells or interpreters (
python,perl,gcc, self-compiled binaries) opening UDPv6 sockets right before a kernel oops; child process of an unprivileged user transitioning to UID 0 afterwards (setuidtransition in auditd).
- Falco/Tracee rule on unusual
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero. The fraggap bytes carried over from the previous skb are copied just past the fragment headers in the new skb's linear area. The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount, and the copy writes past skb->end into the trailing skb_shared_info. An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES. The bad accounting was introduced by commit 773ba4fe9104 ("ipv6: avoid partial copy for zc"). Before commit ce650a166335 ("udp6: Fix __ip6_append_data()'s handling of MSG_SPLICE_PAGES"), the negative copy value caused -EINVAL to be returned. That later commit allowed MSG_SPLICE_PAGES to proceed in this case, making the corruption triggerable. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the paged path, so remove the stale comment describing that old arithmetic. Since a negative copy is no longer expected for a valid MSG_SPLICE_PAGES case, remove the MSG_SPLICE_PAGES exception from the negative copy check.
Source: Ubuntu Security Notices, NVD (NIST), cvelistv5, Microsoft Security Update Guide, redhat_csaf, CISA KEV Catalog, pwn.watch, suse_csaf, siemens_advisory, Debian Security Advisories, Debian LTS Advisories, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Siemens | SIMATIC S7 |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | trixie |
| Linux | debian | linux-6.1 | bullseye |
| Linux | ubuntu | linux-oracle-7.0 | noble |
| Linux | linux | linux_kernel | — |
| Other | siemens | simatic_s7-1500_tm_mfp_firmware | — |
Weakness classes (CWE)
CWE-122Heap-based Buffer Overflow
Variant
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Entry at MITRE CWE-122
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited | |
| PoC-in-GitHub (nomi-sec) | ipv6_frag_escape (opens in a new tab)github.com | PoC (publicly reported)reported, not verified |
References & sources
- git.kernel.orgLinux Kernel — CVE-2026-53362pwn-watch
- git.kernel.orgstable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
- git.kernel.orgstable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
- git.kernel.orgstable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a
- git.kernel.orgstable/c/e9eacf19281ea2498b36291b56c9606118c2d74e
- git.kernel.orgstable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-53362government-resource
- Siemens ProductCERTproductcert/html/ssa-784472.html
- pwn.watchpwn.watch: Linux Kernel: Linux Kernel Unspecified Vulnerabilitypwn-watch
- NVD (NIST)NVD: CVE-2026-53362pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
NVD analysis modifiedNVD
Newly listed as affected:Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Product configuration added —AND OR *cpe:2.3:o:siemens:simatic_s7-1500_tm_mfp_firmware:-:*:*:*:*:*:*:* OR cpe:2.3:h:siemens:simatic_s7-1500_tm_mfp:-:*:*:*:*:*:*:*Reference type added —siemens-SADP: https://cert-portal.siemens.com/productcert/html/ssa-784472.html Types: Third Party AdvisorySource identifier: nvd@nist.gov
Record modifiedSiemens ADP
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/53xxx/CVE-2026-53362.json">CVE-2026-53362</a>Reference added —https://cert-portal.siemens.com/productcert/html/ssa-784472.htmlSource identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
NVD analysis modifiedNVD
Show the original change
Individual changes of this event as published by NVD Type Action Before After Reference type added —CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-53362 Types: US Government ResourceSource identifier: nvd@nist.gov
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment changed {"id":"CVE-2026-53362","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-27T17:44:15.534644Z"}{"id":"CVE-2026-53362","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-27T00:00:00+00:00"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: no
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-53362SSVC assessment changed {"id":"CVE-2026-53362","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-27T13:39:31.757563Z"}{"id":"CVE-2026-53362","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-27T17:44:15.534644Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Show 3 older changes
Record modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) changed Linux, LinuxLinux, LinuxSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Initial analysis by NVDNVD
Newly listed as affected:- Linux Kernel (6.2 – before 6.6.144; 6.7 – before 6.12.95; 6.13 – before 6.18.38; 6.19 – before 7.1.3; 6.0 – before 6.1.177)
New references:- https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962
- https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
- https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a
- https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
and 2 more references
Show 8 original changes
Individual changes of this event as published by NVD Type Action Before After Weakness type (CWE) added —NVD-CWE-noinfoProduct configuration added —OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.144 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.95 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.38 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.1.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.0 up to (excluding) 6.1.177Reference type added —kernel.org: https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e Types: PatchSource identifier: nvd@nist.gov
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962
- https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
- https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a
- https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
and 2 more references
Show 8 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Linux, LinuxDescription added —In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero. The fraggap bytes carried over from the previous skb are copied just past the fragment headers in the new skb's linear area. The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount, and the copy writes past skb->end into the trailing skb_shared_info. An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES. The bad accounting was introduced by commit 773ba4fe9104 ("ipv6: avoid partial copy for zc"). Before commit ce650a166335 ("udp6: Fix __ip6_append_data()'s handling of MSG_SPLICE_PAGES"), the negative copy value caused -EINVAL to be returned. That later commit allowed MSG_SPLICE_PAGES to proceed in this case, making the corruption triggerable. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the paged path, so remove the stale comment describing that old arithmetic. Since a negative copy is no longer expected for a valid MSG_SPLICE_PAGES case, remove the MSG_SPLICE_PAGES exception from the negative copy check.Reference added —https://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962Reference added —https://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993dReference added —https://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0aReference added —https://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769Reference added —https://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5Reference added —https://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74eSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Linked advisories
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-53362"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-53362.svg?lang=en" alt="CVE-2026-53362 – NEOSEC Intel" height="20"></a>