CVE-2026-93824: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-93824 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-93824 at a Glance
How to Fix CVE-2026-93824
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-93824, 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-93824?
Which Software versions are affected?
What version fixes CVE-2026-93824?
What CWE is associated with CVE-2026-93824?
How can I check Maven dependencies for CVE-2026-93824?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-p3wg-3xj5-pf82",
"modified" : "2026-10-03T12:31:10Z",
"published" : "2026-09-24T18:31:31Z",
"aliases" : [ "CVE-2026-93824" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntls: reject the combination of TLS and sockmap\n\nTLS and sockmap (BPF psock) integration hides a lot of latent bugs.\nBugs which may be more or less relevant for real users but they\nare definitely exploitable.\n\nWe could not find anyone actively using this integration so let's\nreject this config. Adding a TLS socket to a sockmap was already\nrejected by sk_psock_init() through the inet_csk_has_ulp() check.\nWe need to reject the attempts to configure the TLS keys (rather\nthan adding the ULP itself) because checking prior to the ULP\ninstallation is tricky without risking a race with sockmap getting\nadded in parallel (sockmap does not hold the socket lock).\n\nThis patch is a minimal rejection of the feature. Subsequent patch\nin the series will do a light dead code removal. Full cleanup would\nrequire a major rewrite of the Tx path, we don't need skmsg any more.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93824"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/460e6486617c17dd19abe8f3fc67d9a6fa25f8ca"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a08e780b6cc1153cbff8be55de9ec9da809e344f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c3d4d537337f69e405a36fa561e7292ee4148bf7"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c4896592744f30ff026f799947c5978bcfd7c8c7"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e26aa709454d48c3b3ef8d3100c8a04e7d9fd94e"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-24T17:17:16Z"
}
}