CVE-2026-80960: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-80960 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-80960 at a Glance
How to Fix CVE-2026-80960
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.
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-80960, 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 General Security Weakness. 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
References
Frequently Asked Questions
What is CVE-2026-80960?
Which Software versions are affected?
What version fixes CVE-2026-80960?
What CWE is associated with CVE-2026-80960?
How can I check Maven dependencies for CVE-2026-80960?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5phx-c495-rgx5",
"modified" : "2026-09-11T21:31:21Z",
"published" : "2026-09-11T21:31:21Z",
"aliases" : [ "CVE-2026-80960" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-pcache: validate on-media seg_num against the cache device size\n\nseg_num is read from the crc32c-only superblock, so whoever supplies the\ncache device on a table load (CAP_SYS_ADMIN) controls it. It sizes\ncache->segments[] and is the value every later on-media segment id is\nbounded against, yet it is never checked against the device. Because\ncache_dev->mapping is the direct map of the pmem, CACHE_DEV_SEGMENT() for\na segment id past the device resolves to ordinary kernel memory beyond\nthe mapping; a new-cache init reaching such an id has cache_seg_init() ->\ncache_dev_zero_range() memset() 12 KiB over that memory -- an\nout-of-bounds write into the kernel heap at table load. A zero seg_num\nmakes the segment allocations ZERO_SIZE_PTR.\n\nReject a seg_num that is zero, larger than the device can hold, or larger\nthan PCACHE_CACHE_SEGS_MAX before it is used.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80960"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/62d92e45abe9e087370f9fc5d876b95673aced34"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/91b93fe5cf4d62d5ecc642a6c8f15a3c11b00e3c"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e889c0ee81165fc90aad2979b51f930f77895703"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-11T20:19:01Z"
}
}