CVE-2026-68122: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-68122 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-68122 at a Glance
How to Fix CVE-2026-68122
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-68122, 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-68122?
Which Software versions are affected?
What version fixes CVE-2026-68122?
What CWE is associated with CVE-2026-68122?
How can I check Maven dependencies for CVE-2026-68122?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-76xv-8vj7-3x63",
"modified" : "2026-08-10T15:33:36Z",
"published" : "2026-08-10T15:33:36Z",
"aliases" : [ "CVE-2026-68122" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\novpn: fix peer refcount leak in TCP error paths\n\nWhen either the TCP RX or TX error path calls ovpn_peer_hold() followed\nby schedule_work(&peer->tcp.defer_del_work), and the work item is already\npending from the other path, schedule_work() returns false and the work\nruns only once. Since ovpn_tcp_peer_del_work() calls ovpn_peer_put()\nexactly once, the extra reference taken by the losing path is never\ndropped, leaking the peer object.\n\nThe race window:\n\n CPU0 (strparser/RX error): CPU1 (tcp_tx_work/TX error):\n ovpn_peer_hold() <- refcnt+1 ovpn_peer_hold() <- refcnt+2\n schedule_work() <- queued schedule_work() <- NO-OP\n (work already pending)\n ovpn_tcp_peer_del_work runs:\n ovpn_peer_del()\n ovpn_peer_put() <- refcnt+1\n <- peer never freed\n\nFix by checking the return value of schedule_work() in both paths and\ncalling ovpn_peer_put() to drop the extra reference if the work was\nalready pending. ovpn_peer_hold() is kept unconditional in the TX path\nas it cannot fail at that point.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68122"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/63bbe18fc03062f483c627838a566a707b62da79"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b08526bf0bbf84ceebd29033783e8e0c9f451286"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f08f39c1f43f3980d46b06af8ed99ffe84ac294a"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-10T13:19:57Z"
}
}