CVE-2026-43315: Software Security Vulnerability Vulnerability
MODERATECVE-2026-43315 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-43315 at a Glance
Security Impact
CVSS: 5.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-43315
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-43315, 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-43315?
Which Software versions are affected?
What version fixes CVE-2026-43315?
What is the CVSS score of CVE-2026-43315?
What CWE is associated with CVE-2026-43315?
How can I check Maven dependencies for CVE-2026-43315?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fmhq-qfjw-fm2x",
"modified" : "2026-05-15T18:30:30Z",
"published" : "2026-05-08T15:31:23Z",
"aliases" : [ "CVE-2026-43315" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding\n\nDrop the WARN in svm_set_nested_state() on nested_svm_load_cr3() failing\nas it is trivially easy to trigger from userspace by modifying CPUID after\nloading CR3. E.g. modifying the state restoration selftest like so:\n\n --- tools/testing/selftests/kvm/x86/state_test.c\n +++ tools/testing/selftests/kvm/x86/state_test.c\n @@ -280,7 +280,16 @@ int main(int argc, char *argv[])\n\n /* Restore state in a new VM. */\n vcpu = vm_recreate_with_one_vcpu(vm);\n - vcpu_load_state(vcpu, state);\n +\n + if (stage == 4) {\n + state->sregs.cr3 = BIT(44);\n + vcpu_load_state(vcpu, state);\n +\n + vcpu_set_cpuid_property(vcpu, X86_PROPERTY_MAX_PHY_ADDR, 36);\n + __vcpu_nested_state_set(vcpu, &state->nested);\n + } else {\n + vcpu_load_state(vcpu, state);\n + }\n\n /*\n * Restore XSAVE state in a dummy vCPU, first without doing\n\ngenerates:\n\n WARNING: CPU: 30 PID: 938 at arch/x86/kvm/svm/nested.c:1877 svm_set_nested_state+0x34a/0x360 [kvm_amd]\n Modules linked in: kvm_amd kvm irqbypass [last unloaded: kvm]\n CPU: 30 UID: 1000 PID: 938 Comm: state_test Tainted: G W 6.18.0-rc7-58e10b63777d-next-vm\n Tainted: [W]=WARN\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n RIP: 0010:svm_set_nested_state+0x34a/0x360 [kvm_amd]\n Call Trace:\n <TASK>\n kvm_arch_vcpu_ioctl+0xf33/0x1700 [kvm]\n kvm_vcpu_ioctl+0x4e6/0x8f0 [kvm]\n __x64_sys_ioctl+0x8f/0xd0\n do_syscall_64+0x61/0xad0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nSimply delete the WARN instead of trying to prevent userspace from shoving\n\"illegal\" state into CR3. For better or worse, KVM's ABI allows userspace\nto set CPUID after SREGS, and vice versa, and KVM is very permissive when\nit comes to guest CPUID. I.e. attempting to enforce the virtual CPU model\nwhen setting CPUID could break userspace. Given that the WARN doesn't\nprovide any meaningful protection for KVM or benefit for userspace, simply\ndrop it even though the odds of breaking userspace are minuscule.\n\nOpportunistically delete a spurious newline.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-43315"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/155ec243ef726f4bc49536fa0bfb565dc011ab17"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/580ea57840864d40e019bc13fd26afdc8d510a2f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/969e5e13ff5c18603f21d1f9f64ec9194e141ac0"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ce904c8a5bbe697eae0f7e34b07095bd7a6dee19"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/deb8f6dfd31d94b18dbeeaa8c01fbec5fc70fd2b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ebb2ab4f1c87d6b52776292cf7dc16aea48e95f8"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fc3ba56385d03501eb582e4b86691ba378e556f9"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "MODERATE",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-05-08T14:16:39Z"
}
}