CVE-2026-64007: Software Security Vulnerability Vulnerability
CRITICALCVE-2026-64007 is a CRITICAL (CVSS 9.8) security vulnerability vulnerability (CWE-416: Use After Free) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-64007 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-64007
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:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-64007, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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 CWE-416: Use After Free, where the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. 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-64007?
Which Software versions are affected?
What version fixes CVE-2026-64007?
What is the CVSS score of CVE-2026-64007?
What CWE is associated with CVE-2026-64007?
How can I check Maven dependencies for CVE-2026-64007?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rf6c-225m-p2p4",
"modified" : "2026-07-20T15:31:55Z",
"published" : "2026-07-19T18:31:49Z",
"aliases" : [ "CVE-2026-64007" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: synproxy: refresh tcphdr after skb_ensure_writable\n\nsynproxy_tstamp_adjust() rewrites the TCP timestamp option in place\nand then patches the TCP checksum via inet_proto_csum_replace4() on\nthe caller-supplied tcphdr pointer. Both ipv4_synproxy_hook() and\nipv6_synproxy_hook() obtain that pointer with skb_header_pointer()\nbefore calling in, so it may either alias skb->head directly or\npoint at the caller's on-stack _tcph buffer.\n\nBetween obtaining the pointer and using it, the function calls\nskb_ensure_writable(skb, optend), which on a cloned or non-linear\nskb invokes pskb_expand_head() and frees the old skb->head. After\nthat point the cached th is stale:\n\n caller (ipv[46]_synproxy_hook)\n th = skb_header_pointer(skb, ..., &_tcph)\n synproxy_tstamp_adjust(skb, protoff, th, ...)\n skb_ensure_writable(skb, optend)\n pskb_expand_head() /* kfree(old skb->head) */\n ...\n inet_proto_csum_replace4(&th->check, ...)\n /* writes into freed head, or\n into the caller's stack copy\n leaving the on-wire checksum\n stale */\n\nThe option bytes are written through skb->data and are fine; only\nthe checksum update goes through th and so lands in the wrong\nplace. The result is either a write into freed slab memory or a\npacket leaving with a checksum that does not match its payload.\n\nFix by re-deriving th from skb->data + protoff immediately after\nskb_ensure_writable() succeeds, so the subsequent checksum update\ntargets the linear, writable header.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64007"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/92170e6afe927ab2792a3f71902845789c8e31b1"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9902a1058992de5d95656b64a3bd95c077f7ba2c"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a91887a5b6ee4b98dfbf1db657ed2b879430149e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/af2c22ccb1f621aff487ff47a040e38e058541e7"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c7f945f7da097245a2f8ed7775ce48421047ee96"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/d3019c61799adc21811af4b521f11f3dc77f8e04"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/dd206819f210522579010d889d45a9530bb494bc"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f0fea2b6d5453a11ad11713bbf37561b9b3a7edf"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-416" ],
"severity" : "CRITICAL",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-07-19T16:17:40Z"
}
}