CVE-2026-53365: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-9p63-4jq7-2c9w
Share
CVSS 5.5
CWE-404 CWE-401
Published
Advisory Summary

CVE-2026-53365 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-404: Improper Resource Shutdown or Release) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not release or incorrectly releases a resource before it is made available for re-use.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-53365 at a Glance

CVE Identifier CVE-2026-53365
GHSA Identifier GHSA-9p63-4jq7-2c9w
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-404: Improper Resource Shutdown or Release
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-53365

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-53365, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-404: Improper Resource Shutdown or Release, where the product does not release or incorrectly releases a resource before it is made available for re-use. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix zerocopy completion for multi-skb sends When a large message is fragmented into multiple skbs, the zerocopy uarg is only allocated and attached to the last skb in the loop. Non-final skbs carry pinned user pages with no completion tracking, so the kernel has no way to notify userspace when those pages are safe to reuse. If the loop breaks early the uarg is never allocated at all, leaking pinned pages with no completion notification. Fix this by following the approach used by TCP: allocate the zerocopy uarg (if not provided by the caller) before the send loop and attach it to every skb via skb_zcopy_set(), which takes a reference per skb. Each skb's completion properly decrements the refcount, and the notification only fires after the last skb is freed. On failure, if no data was sent, the uarg is cleanly aborted via net_zcopy_put_abort(). This issue was initially discovered by sashiko while reviewing commit 1cb36e252211 ("vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting") but was pre-existing.

References

NVD — CVE-2026-53365 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-53365
git.kernel.org/stable/c/293fe8f2d1... WEB
https://git.kernel.org/stable/c/293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9
git.kernel.org/stable/c/76b995bc57... WEB
https://git.kernel.org/stable/c/76b995bc57bd90cb6e954e1966fbd8786da47f0d
git.kernel.org/stable/c/ae38d91791... WEB
https://git.kernel.org/stable/c/ae38d9179190a956e2a87a69ef1dd6f451b51c4d
git.kernel.org/stable/c/b3155f2b78... WEB
https://git.kernel.org/stable/c/b3155f2b78db21e99256bcf7eb902f24ff6d5338
Software Source Repository REPOSITORY
https://github.com/MaherAzzouzi/vsockdrop

Frequently Asked Questions

What is CVE-2026-53365?
CVE-2026-53365 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-404: Improper Resource Shutdown or Release.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-53365?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-53365?
CVE-2026-53365 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-53365?
CVE-2026-53365 is classified under CWE-404: Improper Resource Shutdown or Release (The product does not release or incorrectly releases a resource before it is made available for re-use.).
How can I check Maven dependencies for CVE-2026-53365?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9p63-4jq7-2c9w",
  "modified" : "2026-08-18T15:31:16Z",
  "published" : "2026-07-13T18:30:53Z",
  "aliases" : [ "CVE-2026-53365" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix zerocopy completion for multi-skb sends\n\nWhen a large message is fragmented into multiple skbs, the zerocopy\nuarg is only allocated and attached to the last skb in the loop.\nNon-final skbs carry pinned user pages with no completion tracking,\nso the kernel has no way to notify userspace when those pages are safe\nto reuse. If the loop breaks early the uarg is never allocated at all,\nleaking pinned pages with no completion notification.\n\nFix this by following the approach used by TCP: allocate the zerocopy\nuarg (if not provided by the caller) before the send loop and attach\nit to every skb via skb_zcopy_set(), which takes a reference per skb.\nEach skb's completion properly decrements the refcount, and the\nnotification only fires after the last skb is freed.\nOn failure, if no data was sent, the uarg is cleanly aborted via\nnet_zcopy_put_abort().\n\nThis issue was initially discovered by sashiko while reviewing commit\n1cb36e252211 (\"vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting\")\nbut was pre-existing.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53365"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/76b995bc57bd90cb6e954e1966fbd8786da47f0d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ae38d9179190a956e2a87a69ef1dd6f451b51c4d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b3155f2b78db21e99256bcf7eb902f24ff6d5338"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MaherAzzouzi/vsockdrop"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-401", "CWE-404" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-13T18:16:28Z"
  }
}