CVE-2026-68156: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-rf74-56p2-8jqj
Share
CVSS 9.8
CWE-416
Published
Advisory Summary

CVE-2026-68156 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-68156 at a Glance

CVE Identifier CVE-2026-68156
GHSA Identifier GHSA-rf74-56p2-8jqj
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-416: Use After Free
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

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).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-68156

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.

Verify Direct and Transitive Dependencies

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-68156, 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 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

In the Linux kernel, the following vulnerability has been resolved: libceph: refresh auth->authorizer_buf{,_len} after authorizer update ceph_x_create_authorizer() caches au->buf->vec.iov_base and au->buf->vec.iov_len in struct ceph_auth_handshake. These cached values are then used by the messenger connect code when sending the authorizer. ceph_x_update_authorizer() can rebuild the authorizer when a newer service ticket is available. If the rebuilt authorizer no longer fits in the existing buffer, ceph_x_build_authorizer() drops its reference to au->buf and allocates a new one. If this is the final reference, ceph_buffer_put() frees the old ceph_buffer and its vec.iov_base, but auth->authorizer_buf still points at that freed memory. A subsequent msgr1 reconnect can therefore queue the stale pointer and trigger a KASAN slab-use-after-free in _copy_from_iter() while tcp_sendmsg() copies the authorizer. Refresh auth->authorizer_buf and auth->authorizer_buf_len after a successful authorizer rebuild so the messenger sends the current buffer.

References

NVD — CVE-2026-68156 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68156
git.kernel.org/stable/c/0060ec9122... WEB
https://git.kernel.org/stable/c/0060ec912292a550198d8d18ac95b433c92a7091
git.kernel.org/stable/c/2334e99973... WEB
https://git.kernel.org/stable/c/2334e9997308305ee4fd508fdfe6086c4150ed60
git.kernel.org/stable/c/26f814187a... WEB
https://git.kernel.org/stable/c/26f814187abceee90dbb29a02133adb4786fbb13
git.kernel.org/stable/c/5ecfcd5c05... WEB
https://git.kernel.org/stable/c/5ecfcd5c05866f185357700b81b461dae4f5ebb2
git.kernel.org/stable/c/75e82e8944... WEB
https://git.kernel.org/stable/c/75e82e8944ac1efe9fdb88bd2f14d9a031282bdf
git.kernel.org/stable/c/79a273df64... WEB
https://git.kernel.org/stable/c/79a273df64238a4ade8b709689a78589f755b8ef
git.kernel.org/stable/c/937d61f86d... WEB
https://git.kernel.org/stable/c/937d61f86d377a3aa578adae7a3dfcecdddf9d89
git.kernel.org/stable/c/9d37aec9ff... WEB
https://git.kernel.org/stable/c/9d37aec9ffe4e743dabc3f84502e9723e17a30d4

Frequently Asked Questions

What is CVE-2026-68156?
CVE-2026-68156 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-416: Use After Free.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68156?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-68156?
CVE-2026-68156 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-68156?
CVE-2026-68156 is classified under CWE-416: Use After Free (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.).
How can I check Maven dependencies for CVE-2026-68156?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rf74-56p2-8jqj",
  "modified" : "2026-08-19T18:32:08Z",
  "published" : "2026-08-10T15:33:38Z",
  "aliases" : [ "CVE-2026-68156" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: refresh auth->authorizer_buf{,_len} after authorizer update\n\nceph_x_create_authorizer() caches au->buf->vec.iov_base and\nau->buf->vec.iov_len in struct ceph_auth_handshake.  These\ncached values are then used by the messenger connect code when\nsending the authorizer.\n\nceph_x_update_authorizer() can rebuild the authorizer when a newer\nservice ticket is available.  If the rebuilt authorizer no longer\nfits in the existing buffer, ceph_x_build_authorizer() drops its\nreference to au->buf and allocates a new one.  If this is the final\nreference, ceph_buffer_put() frees the old ceph_buffer and its\nvec.iov_base, but auth->authorizer_buf still points at that freed\nmemory.\n\nA subsequent msgr1 reconnect can therefore queue the stale pointer\nand trigger a KASAN slab-use-after-free in _copy_from_iter() while\ntcp_sendmsg() copies the authorizer.\n\nRefresh auth->authorizer_buf and auth->authorizer_buf_len after a\nsuccessful authorizer rebuild so the messenger sends the current\nbuffer.",
  "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-68156"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0060ec912292a550198d8d18ac95b433c92a7091"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2334e9997308305ee4fd508fdfe6086c4150ed60"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/26f814187abceee90dbb29a02133adb4786fbb13"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5ecfcd5c05866f185357700b81b461dae4f5ebb2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/75e82e8944ac1efe9fdb88bd2f14d9a031282bdf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/79a273df64238a4ade8b709689a78589f755b8ef"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/937d61f86d377a3aa578adae7a3dfcecdddf9d89"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9d37aec9ffe4e743dabc3f84502e9723e17a30d4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-416" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:01Z"
  }
}