CVE-2026-98274: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98274 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-98274 at a Glance
How to Fix CVE-2026-98274
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-98274, 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-98274?
Which Software versions are affected?
What version fixes CVE-2026-98274?
What CWE is associated with CVE-2026-98274?
How can I check Maven dependencies for CVE-2026-98274?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-566p-8rmw-5xmj",
"modified" : "2026-10-06T09:31:33Z",
"published" : "2026-10-06T09:31:33Z",
"aliases" : [ "CVE-2026-98274" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: psp: avoid conflicts with skb->decrypted and sk_validate_xmit_skb()\n\nPSP conflicts with TLS ULP in its usage of both skb->decrypted and\nsk->sk_validate_xmit_skb().\n\nMake PSP mutually exclusive with TLS ULP, the only other user of either\nof these. As other users of skb->decrypted come along, they can be added\nto sk_has_decrypt_user(). It would make sense to also assert that\nsk->sk_validate_xmit_skb() is also NULL in both of these setup paths for\nsimilar future proofing, but the PSP listener/sk_clone() path is still\nbroken and it could be seen as a regression to not allow rx assoc to run\non a child of a listener socket with PSP tx assoc state.\n\nInclude all TCP ULPs in the sk_has_decrypt_user() check, even though TLS\nis the only one that conflicts with PSP via the decrypted bit. This is\nintentional because PSP was not designed to be used with ULPs. It is\nbest to close off surface area that may make bugs reachable, until\nsomeone wishes to design and test an actual user of PSP with ULPs.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98274"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a13cca5ba5375f13cbdab545abfb5e288bef3f78"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a41f24c612c3f5139a3143307eb85bbcf1bd4d07"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c8c8c18862337c469e325c207601de3279847809"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-06T09:18:17Z"
}
}