CVE-2026-74729: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-74729 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-74729 at a Glance
How to Fix CVE-2026-74729
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-74729, 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-74729?
Which Software versions are affected?
What version fixes CVE-2026-74729?
What CWE is associated with CVE-2026-74729?
How can I check Maven dependencies for CVE-2026-74729?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-6hj9-w6w6-x26p",
"modified" : "2026-10-15T12:30:44Z",
"published" : "2026-08-22T18:30:30Z",
"aliases" : [ "CVE-2026-74729" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsoc: aspeed: lpc-snoop: Fix usercopy overflow in snoop_file_read\n\nput_fifo_with_discard() acts as both producer and consumer on the kfifo:\nit calls kfifo_skip() (advances out) and kfifo_put() (advances in) from\nthe IRQ handler without synchronizing with snoop_file_read(), which also\nconsumes via kfifo_to_user(). On SMP systems this concurrent access can\nleave (in - out) larger than the ring buffer, so __kfifo_to_user()'s clamp\nto (in - out) is ineffective and kfifo_copy_to_user() can attempt a\ncopy_to_user() past the kmalloc-2k backing store:\n\n usercopy: Kernel memory exposure attempt detected from SLUB object\n 'kmalloc-2k' (offset 0, size 2049)!\n kernel BUG at mm/usercopy.c!\n Call trace:\n usercopy_abort\n __check_heap_object\n __check_object_size\n kfifo_copy_to_user\n __kfifo_to_user\n snoop_file_read\n vfs_read\n\nSerialize kfifo access with a per-channel spinlock shared between the\nIRQ handler (producer) and the file reader (consumer). Annotate @fifo\nwith __guarded_by(&lock) and opt the driver into context analysis so the\ncompiler enforces that all fifo access holds the lock.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74729"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/131ab677b03349a5ae48da8722ec7075b37ec66e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/1acef6d85bfd98bd9dfe1f08bffa397a4dda8a6f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/868c478abce858135db3eb65548a577e4b6747ac"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-22T16:16:48Z"
}
}