CVE-2026-72183: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-5hcp-6cc5-jgx7
CVSS 8.4
Published
Advisory Summary

CVE-2026-72183 is a HIGH (CVSS 8.4) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-72183 at a Glance

CVE Identifier CVE-2026-72183
GHSA Identifier GHSA-5hcp-6cc5-jgx7
Severity HIGH
CVSS v3.1 Base Score 8.4
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H).

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

How to Fix CVE-2026-72183

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-72183, 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: landlock: Fix LANDLOCK_SCOPE_SIGNAL bypass on the SIGIO path LANDLOCK_SCOPE_SIGNAL must prevent a sandboxed process from signaling processes outside its Landlock domain. It can be bypassed through the asynchronous SIGIO delivery path. A sandboxed process that owns any file or socket can arm it with fcntl(fd, F_SETOWN, -pgid), fcntl(fd, F_SETSIG, SIGKILL) and O_ASYNC, so that an I/O event makes the kernel deliver the chosen signal to the whole process group. As the head of its process group's task list (the default position right after fork()) that group can also hold the non-sandboxed process that launched it, e.g. a supervisor or a security monitor. The sandbox can thus kill or signal the processes LANDLOCK_SCOPE_SIGNAL is meant to protect from it. The scope is enforced in hook_file_send_sigiotask() against the Landlock domain recorded at F_SETOWN time, not the live domain of the sender. control_current_fowner() decides whether to record that domain and skips recording it when the fowner target is in the caller's thread group, which is safe only for a single-task target (PIDTYPE_PID, PIDTYPE_TGID). For a process group (PIDTYPE_PGID) pid_task() returns only one member; recording is skipped whenever that member shares the caller's thread group, and hook_file_send_sigiotask() then lets the signal fan out to the whole group unchecked. Record the domain for every non single-process target so the scope is enforced against each group member at delivery time. That recording is necessary but not sufficient on its own: the kernel signals a process group through its members' thread-group leaders, and the leader of the registrant's own process can carry a different Landlock domain than the sibling thread that armed the owner. domain_is_scoped() would then deny that leader, even though commit 18eb75f3af40 ("landlock: Always allow signals between threads of the same process") requires same-process delivery to be allowed. hook_task_kill() avoids this by evaluating same_thread_group() live, per recipient; the SIGIO path instead delegates the whole decision to a single registration-time check, which a process-group fan-out cannot honor. So also record the registrant's thread group next to its domain and exempt it at delivery: hook_file_send_sigiotask() allows the signal whenever the recipient belongs to the registrant's own process, restoring the same-process guarantee while keeping out-of-domain group members blocked. The direct kill() path (hook_task_kill) already evaluates the live domain and is unaffected. [mic: Check pid_type earlier and improve comment, fix commit message, fix comment formatting]

References

Frequently Asked Questions

What is CVE-2026-72183?
CVE-2026-72183 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-72183?
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-72183?
CVE-2026-72183 has a CVSS v3.1 base score of 8.4 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H.
What CWE is associated with CVE-2026-72183?
CVE-2026-72183 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72183?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5hcp-6cc5-jgx7",
  "modified" : "2026-08-17T06:33:14Z",
  "published" : "2026-08-15T06:32:15Z",
  "aliases" : [ "CVE-2026-72183" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nlandlock: Fix LANDLOCK_SCOPE_SIGNAL bypass on the SIGIO path\n\nLANDLOCK_SCOPE_SIGNAL must prevent a sandboxed process from signaling\nprocesses outside its Landlock domain.  It can be bypassed through the\nasynchronous SIGIO delivery path.\n\nA sandboxed process that owns any file or socket can arm it with\nfcntl(fd, F_SETOWN, -pgid), fcntl(fd, F_SETSIG, SIGKILL) and O_ASYNC, so\nthat an I/O event makes the kernel deliver the chosen signal to the\nwhole process group.  As the head of its process group's task list (the\ndefault position right after fork()) that group can also hold the\nnon-sandboxed process that launched it, e.g. a supervisor or a security\nmonitor.  The sandbox can thus kill or signal the processes\nLANDLOCK_SCOPE_SIGNAL is meant to protect from it.\n\nThe scope is enforced in hook_file_send_sigiotask() against the Landlock\ndomain recorded at F_SETOWN time, not the live domain of the sender.\ncontrol_current_fowner() decides whether to record that domain and skips\nrecording it when the fowner target is in the caller's thread group,\nwhich is safe only for a single-task target (PIDTYPE_PID, PIDTYPE_TGID).\nFor a process group (PIDTYPE_PGID) pid_task() returns only one member;\nrecording is skipped whenever that member shares the caller's thread\ngroup, and hook_file_send_sigiotask() then lets the signal fan out to\nthe whole group unchecked.\n\nRecord the domain for every non single-process target so the scope is\nenforced against each group member at delivery time.\n\nThat recording is necessary but not sufficient on its own: the kernel\nsignals a process group through its members' thread-group leaders, and\nthe leader of the registrant's own process can carry a different\nLandlock domain than the sibling thread that armed the owner.\ndomain_is_scoped() would then deny that leader, even though commit\n18eb75f3af40 (\"landlock: Always allow signals between threads of the\nsame process\") requires same-process delivery to be allowed.\nhook_task_kill() avoids this by evaluating same_thread_group() live, per\nrecipient; the SIGIO path instead delegates the whole decision to a\nsingle registration-time check, which a process-group fan-out cannot\nhonor.\n\nSo also record the registrant's thread group next to its domain and\nexempt it at delivery: hook_file_send_sigiotask() allows the signal\nwhenever the recipient belongs to the registrant's own process,\nrestoring the same-process guarantee while keeping out-of-domain group\nmembers blocked.  The direct kill() path (hook_task_kill) already\nevaluates the live domain and is unaffected.\n\n[mic: Check pid_type earlier and improve comment, fix commit message,\nfix comment formatting]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72183"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/04916f7dc6d37cd478b06c86398c34a6963ac8c9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1f18aac2637220b5847d073447498e81ddca10b2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4b80320ca7ed03d6e683f95b6066565dc97b9f92"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7a92e9fd1d496a610b40e0c4253fd54e7496f5ab"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:36Z"
  }
}