CVE-2026-53244: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-q9qr-5342-rrw2
Share
CVSS 7.5
Published
Advisory Summary

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

CVE-2026-53244 at a Glance

CVE Identifier CVE-2026-53244
GHSA Identifier GHSA-q9qr-5342-rrw2
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

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:N/I:N/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 None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-53244

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-53244, 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: VFS: fix possible failure to unlock in nfsd4_create_file() atomic_create() in fs/namei.c drops the reference to the dentry when it returns an error. This behaviour was imported into dentry_create() so that it will drop the reference if an error is returned from atomic_create(), though not if vfs_create() returns an error (in the case where ->atomic_create is not supported). The caller - nfsd4_create_file() - is made aware of this by checking path->dentry, which will either be a counted reference to a dentry, or an error pointer. However the change to use start_creating()/end_creating() (which landed shortly before the dentry_create() change landed, though was likely developed around the same time) means that nfsd4_create_file() *needs* a valid dentry so that it can unlock the parent. The net result is that if NFSD exports a filesystem which uses ->atomic_create, and if a call to ->atomic_create returns an error, then nfsd4_create_file() will pass an error pointer to end_creating() and the parent will not be unlocked. Fix this by changing dentry_create() to make sure path->dentry is always a valid dentry, never an error-pointer. The actual error is already returned a different way. Note that if ->atomic_create() returns a different dentry (which may not be possible in practice) we are guaranteed (because it is only ever provided by d_spliace_alias()) that it will have the same d_parent and so it will have the same effect when passed to end_creating().

References

NVD — CVE-2026-53244 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-53244
git.kernel.org/stable/c/e824bbd4d2... WEB
https://git.kernel.org/stable/c/e824bbd4d224cce4b5fb59cc9dcd3447fe0b7e44
git.kernel.org/stable/c/ee1f40759a... WEB
https://git.kernel.org/stable/c/ee1f40759a50b1800c98c1c369afd5b3e44ad987

Frequently Asked Questions

What is CVE-2026-53244?
CVE-2026-53244 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-53244?
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-53244?
CVE-2026-53244 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-53244?
CVE-2026-53244 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-53244?
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-q9qr-5342-rrw2",
  "modified" : "2026-06-28T09:31:46Z",
  "published" : "2026-06-25T09:31:22Z",
  "aliases" : [ "CVE-2026-53244" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nVFS: fix possible failure to unlock in nfsd4_create_file()\n\natomic_create() in fs/namei.c drops the reference to the dentry\nwhen it returns an error.\nThis behaviour was imported into dentry_create() so that it\nwill drop the reference if an error is returned from atomic_create(),\nthough not if vfs_create() returns an error (in the case where\n->atomic_create is not supported).\n\nThe caller - nfsd4_create_file() - is made aware of this by checking\npath->dentry, which will either be a counted reference to a dentry, or\nan error pointer.\n\nHowever the change to use start_creating()/end_creating() (which landed\nshortly before the dentry_create() change landed, though was likely\ndeveloped around the same time) means that nfsd4_create_file() *needs* a\nvalid dentry so that it can unlock the parent.\n\nThe net result is that if NFSD exports a filesystem which uses\n->atomic_create, and if a call to ->atomic_create returns an error, then\nnfsd4_create_file() will pass an error pointer to end_creating()\nand the parent will not be unlocked.\n\nFix this by changing dentry_create() to make sure path->dentry is always\na valid dentry, never an error-pointer.  The actual error is already\nreturned a different way.\n\nNote that if ->atomic_create() returns a different dentry (which may not\nbe possible in practice) we are guaranteed (because it is only ever\nprovided by d_spliace_alias()) that it will have the same d_parent and\nso it will have the same effect when passed to end_creating().",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53244"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e824bbd4d224cce4b5fb59cc9dcd3447fe0b7e44"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ee1f40759a50b1800c98c1c369afd5b3e44ad987"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-25T09:16:42Z"
  }
}