CVE-2026-74754: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-74754 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-74754 at a Glance
How to Fix CVE-2026-74754
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-74754, 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-74754?
Which Software versions are affected?
What version fixes CVE-2026-74754?
What CWE is associated with CVE-2026-74754?
How can I check Maven dependencies for CVE-2026-74754?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5jqh-pxwf-wg8m",
"modified" : "2026-10-15T12:30:44Z",
"published" : "2026-10-15T12:30:44Z",
"aliases" : [ "CVE-2026-74754" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: pair EH runtime PM get and put\n\nshost->eh_noresume is currently consulted twice in one error handling\niteration: once before scsi_autopm_get_host() and once again before\nscsi_autopm_put_host().\n\nThat is racy when a PM-triggered error path flips shost->eh_noresume\nwhile the SCSI EH thread is still running.\n\nThe problem flow looks like this:\nPM path\n ufshcd_set_dev_pwr_mode()\n shost->eh_noresume = 1\n ufshcd_execute_start_stop <-- trigger EH\n ...\n shost->eh_noresume = 0\n\nEH path\n scsi_error_handler()\n if (!shost->eh_noresume)\n scsi_autopm_get_host() <-- skipped\n ...\n if (!shost->eh_noresume)\n scsi_autopm_put_host() <-- executed later\n\nIn that case one EH iteration can skip autoresume on entry and still\ndrop a runtime PM reference on exit. That leaves an unmatched runtime PM\nput and can trigger a runtime PM usage count underflow.\n\nFix this by making eh_noresume a regular bool so it can be accessed with\nREAD_ONCE() and WRITE_ONCE(). Snapshot it once per EH iteration and use\nthat snapshot for both runtime PM get and put decisions.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74754"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/872f486259ae0bc6b73ca4735a15d013241f73e9"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e83eed1bea142c8fe852fd53156845b88252ecd8"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fdc93f4a801077efbf1b87570ade8d8f325de62f"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-26T15:16:54Z"
}
}