CVE-2026-93119: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-93119 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-93119 at a Glance
How to Fix CVE-2026-93119
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-93119, 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-93119?
Which Software versions are affected?
What version fixes CVE-2026-93119?
What CWE is associated with CVE-2026-93119?
How can I check Maven dependencies for CVE-2026-93119?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8rmh-4r43-9cj7",
"modified" : "2026-09-17T18:32:11Z",
"published" : "2026-09-17T18:32:11Z",
"aliases" : [ "CVE-2026-93119" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: ljca: bound bank_num in ljca_enumerate_gpio()\n\nljca_enumerate_gpio() reads desc->bank_num from the device and loops\nvalid_pin[i] = get_unaligned_le32(...) for i < bank_num. valid_pin[]\nholds only LJCA_MAX_GPIO_NUM / 32 = 2 entries.\n\nTwo checks run before the loop. The reply length must match\nstruct_size(desc, bank_desc, bank_num). The product\npins_per_bank * bank_num must not exceed LJCA_MAX_GPIO_NUM. Neither one\nbounds bank_num against the size of valid_pin[]. The reply is capped at\nLJCA_MAX_PAYLOAD_SIZE (60) bytes, so the struct_size check limits\nbank_num to 9. A device that reports bank_num 9 with pins_per_bank 7\nstill passes both checks. gpio_num is 63 and the reply is 56 bytes. The\nloop then writes nine u32 into the two entry array and overruns\nvalid_pin[] on the stack.\n\nA broken or malicious LJCA device can therefore overflow the stack.\nReject a bank_num that does not fit valid_pin[].",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93119"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/0069593170a3d177de793c9a0b36989c4f069111"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9c4bc8f7426aa001387800bf0140bfc5087a6de3"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/aed958c4f784a29cf42abb3e54af51a16bddde46"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/dd9483726d0f16c1a56879c3edb65128259a4e2b"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:18:06Z"
}
}