CVE-2026-93273: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-93273 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-93273 at a Glance
How to Fix CVE-2026-93273
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-93273, 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-93273?
Which Software versions are affected?
What version fixes CVE-2026-93273?
What CWE is associated with CVE-2026-93273?
How can I check Maven dependencies for CVE-2026-93273?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f775-wj9m-j2c6",
"modified" : "2026-09-24T18:31:25Z",
"published" : "2026-09-24T18:31:25Z",
"aliases" : [ "CVE-2026-93273" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nregulator: tps6594: Fix device node reference leaks in multiphase loop\n\nIn tps6594_regulator_probe(), the multi-phase configuration loop calls\nof_find_node_by_name() to find buck nodes by name, and of_get_parent()\ntwice to navigate to the PMIC parent node. None of the acquired node\nreferences (np, intermediate parent, np_pmic_parent) are ever released\nvia of_node_put(), causing a reference leak on every loop iteration.\n\nAdditionally, of_find_node_by_name() can return NULL, but the result was\nimmediately passed to of_node_full_name() and of_get_parent() without a\nNULL check, which could lead to a NULL pointer dereference.\n\nFix this by:\n- Adding a NULL check for np after of_find_node_by_name()\n- Storing the intermediate parent node in a local variable np_parent\n- Calling of_node_put() on np, np_parent and np_pmic_parent at the\n end of each loop iteration",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93273"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/28f70e0aa767a8f022c70ed75ecef227dc668121"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/4a672bff99f6b58dde419fd12b3a53da137f032d"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/68ce4f8223b78f8616ec7f4a02c38988eae627d2"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7fd28093b3effc4f92566466df364622830ec608"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fceac25487b21d6db940d2aed368e465d89cd1f4"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-24T16:17:24Z"
}
}