CVE-2026-68171: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-r2jg-pf44-vfj6
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-68171
GHSA Identifier GHSA-r2jg-pf44-vfj6
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-68171

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

In the Linux kernel, the following vulnerability has been resolved: arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates When seccomp support was originally added to arm64 in a1ae65b21941 ("arm64: add seccomp support"), seccomp was erroneously called _before_ the ptrace syscall-enter-stop and therefore the tracer could trivially manipulate the syscall register state after the seccomp check had passed. This was subsequently fixed in a5cd110cb836 ("arm64/ptrace: run seccomp after ptrace") by moving the seccomp check after the tracer has run. Unfortunately, a decade later, that fix has been reported to be incomplete. On arm64, both the first argument to a syscall and its eventual return value are allocated to register x0. In order to facilitate syscall restarting and querying of syscall arguments on the syscall exit path, the original value of x0 is stashed in 'struct pt_regs::orig_x0' early during the syscall entry path and is returned for the first argument by syscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not directly exposed via ptrace() and so changes to register x0 made by the tracer on a syscall-enter-stop are not reflected in 'orig_x0'. This means that seccomp, syscall tracepoints and audit can observe a stale value for the register compared to the argument that will be observed by the actual syscall. Re-sync 'orig_x0' from x0 on the syscall entry path following a potential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or SECCOMP_RET_TRACE). This behaviour is limited to native tasks (because compat tasks expose 'orig_r0' to ptrace) where the syscall is not being skipped (because x0 is updated to hold the return value of -ENOSYS in that case).

References

NVD — CVE-2026-68171 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68171
git.kernel.org/stable/c/64ab0964c7... WEB
https://git.kernel.org/stable/c/64ab0964c7db949abbd3c56268a220e2b77f7b9e
git.kernel.org/stable/c/8000a5f4d1... WEB
https://git.kernel.org/stable/c/8000a5f4d1d192f5bb3e4f29e7606a9460d376df
git.kernel.org/stable/c/b7afd2a805... WEB
https://git.kernel.org/stable/c/b7afd2a80593dde3f4a68c9a9f73752f9c340e85
git.kernel.org/stable/c/e057b94772... WEB
https://git.kernel.org/stable/c/e057b94772328221405b067c3a85fe479b915dc8
git.kernel.org/stable/c/e59c2476ef... WEB
https://git.kernel.org/stable/c/e59c2476ef755221da31f4e26f6b89712ecf50f1

Frequently Asked Questions

What is CVE-2026-68171?
CVE-2026-68171 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68171?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68171?
CVE-2026-68171 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68171?
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-r2jg-pf44-vfj6",
  "modified" : "2026-08-10T15:33:39Z",
  "published" : "2026-08-10T15:33:39Z",
  "aliases" : [ "CVE-2026-68171" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: syscall: Ensure saved x0 is kept in-sync with tracer updates\n\nWhen seccomp support was originally added to arm64 in a1ae65b21941\n(\"arm64: add seccomp support\"), seccomp was erroneously called _before_\nthe ptrace syscall-enter-stop and therefore the tracer could trivially\nmanipulate the syscall register state after the seccomp check had\npassed. This was subsequently fixed in a5cd110cb836 (\"arm64/ptrace: run\nseccomp after ptrace\") by moving the seccomp check after the tracer has\nrun. Unfortunately, a decade later, that fix has been reported to be\nincomplete.\n\nOn arm64, both the first argument to a syscall and its eventual return\nvalue are allocated to register x0. In order to facilitate syscall\nrestarting and querying of syscall arguments on the syscall exit path,\nthe original value of x0 is stashed in 'struct pt_regs::orig_x0' early\nduring the syscall entry path and is returned for the first argument by\nsyscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not\ndirectly exposed via ptrace() and so changes to register x0 made by the\ntracer on a syscall-enter-stop are not reflected in 'orig_x0'. This\nmeans that seccomp, syscall tracepoints and audit can observe a stale\nvalue for the register compared to the argument that will be observed by\nthe actual syscall.\n\nRe-sync 'orig_x0' from x0 on the syscall entry path following a\npotential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or\nSECCOMP_RET_TRACE). This behaviour is limited to native tasks (because\ncompat tasks expose 'orig_r0' to ptrace) where the syscall is not being\nskipped (because x0 is updated to hold the return value of -ENOSYS in\nthat case).",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68171"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/64ab0964c7db949abbd3c56268a220e2b77f7b9e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8000a5f4d1d192f5bb3e4f29e7606a9460d376df"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b7afd2a80593dde3f4a68c9a9f73752f9c340e85"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e057b94772328221405b067c3a85fe479b915dc8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e59c2476ef755221da31f4e26f6b89712ecf50f1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:03Z"
  }
}