Evidence used
- CISA confirms exploitation in the wild.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.71% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-53362High confidence
Linux Kernel Unspecified Vulnerability
Linux · Kernel
7.8HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productCISA confirms exploitation in the wild and lists 2026-08-30 as the remediation due date. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 27 Aug 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Linux Kernel and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Canonical Ubuntu Security: 20 affected package states with no published fix
Distribution package intelligence
24 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.12.95-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.1.177-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.1.3-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.1.3-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-aws | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-fde | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-nvidia | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gcp | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gke | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gkeop | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-ibm | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-lowlatency | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-lowlatency | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-tegra | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oem-6.11 | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oracle | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-realtime | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-riscv | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-xilinx | Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-53362 · CSAF 2.0 · revision 24 · interimSUSE Product Security TeamCVE-2026-53362
The vendor explicitly identifies these products as affected by this CVE.
- SUSE Linux Micro Extras 6.2:kernel-obs-build
- SUSE Linux Micro Extras 6.2:kernel-syms
- SLES 15 SP1 CHOST Images for Amazon EC2
- SLES 15 SP2 CHOST Images for Amazon EC2
- SLES 15 SP3 CHOST Images for Amazon EC2
- SLES 15 SP4 CHOST Images for Amazon EC2
- SLES 15 SP5 CHOST Images for Amazon EC2
- SLES 15 SP1 CHOST Images for Google
- SLES 15 SP2 CHOST Images for Google
- SLES 15 SP3 CHOST Images for Google
- SLES 15 SP4 CHOST Images for Google
- SLES 15 SP5 CHOST Images for Google
- Summary
- 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.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-53362 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: kernel: ipv6 frag escape
The vendor explicitly identifies these products or versions as containing the fix.
- kernel-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-0:6.12.0-231.14.el10nv.src as a component of NVIDIA for RHEL 10
- kernel-64k-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-core-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debug-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debug-core-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debug-debuginfo-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debug-modules-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debug-modules-core-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debug-modules-extra-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-debuginfo-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- kernel-64k-modules-0:6.12.0-231.14.el10nv.aarch64 as a component of NVIDIA for RHEL 10
- Summary
- A flaw was found in the Linux kernel's ipv6 networking subsystem. An incorrect parameter length calculation allows an attacker with permissions to create UDP sockets to trigger overwrites of kernel memory, potentially leading to privilege escalation, data corruption, or a system crash.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
CISA confirms exploitation in the wild and lists 2026-08-30 as the remediation due date. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Linux Kernel contains an unspecified vulnerability that can allow for privilege escalation via IPv6 networking subsystem. This vulnerability can impact multiple products, including but not limited to Suse, Red Hat, and other products using Linux.
What
Linux Kernel contains an unspecified vulnerability that can allow for privilege escalation via IPv6 networking subsystem. This vulnerability can impact multiple products, including but not limited to Suse, Red Hat, and other products using Linux.
Why
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().
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.
What
Linux Kernel contains an unspecified vulnerability that can allow for privilege escalation via IPv6 networking subsystem. This vulnerability can impact multiple products, including but not limited to Suse, Red Hat, and other products using Linux.
Why
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().
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-08-27.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Heap-based Buffer Overflow → gain additional privileges
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-122 ↗
CWE-122: Heap-based Buffer Overflow. 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().
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- SUSE Linux Micro Extras 6.2:kernel-obs-build
- SUSE Linux Micro Extras 6.2:kernel-syms
- SLES 15 SP1 CHOST Images for Amazon EC2
- SLES 15 SP2 CHOST Images for Amazon EC2
- SLES 15 SP3 CHOST Images for Amazon EC2
- SLES 15 SP4 CHOST Images for Amazon EC2
- SLES 15 SP5 CHOST Images for Amazon EC2
- SLES 15 SP1 CHOST Images for Google
- SLES 15 SP2 CHOST Images for Google
- SLES 15 SP3 CHOST Images for Google
- SLES 15 SP4 CHOST Images for Google
- SLES 15 SP5 CHOST Images for Google
- SLES 15 SP1 CHOST Images for Microsoft Azure
- SLES 15 SP2 CHOST Images for Microsoft Azure
- SLES 15 SP3 CHOST Images for Microsoft Azure
- SLES 15 SP4 CHOST Images for Microsoft Azure
- SLES 15 SP5 CHOST Images for Microsoft Azure
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 4 Jul 2026 · Last source change 28 Aug 2026, 16:52 UTC · CWE-122 · Heap-based Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-41669
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 14200d435af9a9eeb444f529fc2f689a236b7962; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 65fb14cbebb0cd0eff903a22d33537ddc8b95769; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 46f201f8b4c39633a1fa3dc12459f506d470993d; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 6374fb9edf72c67a118a2c214a0dddd04c921e0a; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < e9eacf19281ea2498b36291b56c9606118c2d74e; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 736b380e28d0480c7bc3e022f1950f31fe53a7c5; 6.0 · Fixed: < 6.0; 6.1.177 ≤ 6.1.*; 6.6.144 ≤ 6.6.*; 6.12.95 ≤ 6.12.*; 6.18.38 ≤ 6.18.*; 7.1.3 ≤ 7.1.*; 7.2 ≤ *
- After
- Linux: 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 14200d435af9a9eeb444f529fc2f689a236b7962, 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 65fb14cbebb0cd0eff903a22d33537ddc8b95769, 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 46f201f8b4c39633a1fa3dc12459f506d470993d, 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 6374fb9edf72c67a118a2c214a0dddd04c921e0a, 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < e9eacf19281ea2498b36291b56c9606118c2d74e, 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 736b380e28d0480c7bc3e022f1950f31fe53a7c5, 6.0 · Fixed: Linux: < 6.0, 6.1.177 ≤ 6.1.*, 6.6.144 ≤ 6.6.*, 6.12.95 ≤ 6.12.*, 6.18.38 ≤ 6.18.*, 7.1.3 ≤ 7.1.*, 7.2 ≤ *
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.ENISA EUVD ↗
- Before
- not listed in ENISA EUVD known-exploited dataset
- After
- listed in ENISA EUVD known-exploited dataset (EUVD-2026-41669)
- CISA KEV stateCISA KEV now confirms exploitation in the wild.CISA KEV ↗
- Before
- not listed in CISA KEV
- After
- listed in CISA KEV since 2026-08-27
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 14200d435af9a9eeb444f529fc2f689a236b7962; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 65fb14cbebb0cd0eff903a22d33537ddc8b95769; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 46f201f8b4c39633a1fa3dc12459f506d470993d; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 6374fb9edf72c67a118a2c214a0dddd04c921e0a; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < e9eacf19281ea2498b36291b56c9606118c2d74e; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 736b380e28d0480c7bc3e022f1950f31fe53a7c5; 6.0 · Fixed: < 6.0; 6.1.177 ≤ 6.1.*; 6.6.144 ≤ 6.6.*; 6.12.95 ≤ 6.12.*; 6.18.38 ≤ 6.18.*; 7.1.3 ≤ 7.1.*; 7.2-rc1 ≤ *
- After
- 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 14200d435af9a9eeb444f529fc2f689a236b7962; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 65fb14cbebb0cd0eff903a22d33537ddc8b95769; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 46f201f8b4c39633a1fa3dc12459f506d470993d; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 6374fb9edf72c67a118a2c214a0dddd04c921e0a; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < e9eacf19281ea2498b36291b56c9606118c2d74e; 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 736b380e28d0480c7bc3e022f1950f31fe53a7c5; 6.0 · Fixed: < 6.0; 6.1.177 ≤ 6.1.*; 6.6.144 ≤ 6.6.*; 6.12.95 ≤ 6.12.*; 6.18.38 ≤ 6.18.*; 7.1.3 ≤ 7.1.*; 7.2 ≤ *
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.