CVE-2026-31714: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-48wq-5h48-mwqq
Share
CVSS 5.5
CWE-401
Published
Advisory Summary

CVE-2026-31714 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-401: Missing Release of Memory after Effective Lifetime) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-31714 at a Glance

CVE Identifier CVE-2026-31714
GHSA Identifier GHSA-48wq-5h48-mwqq
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-401: Missing Release of Memory after Effective Lifetime
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
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-31714

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-31714, 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-401: Missing Release of Memory after Effective Lifetime, where the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. 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: f2fs: fix to avoid memory leak in f2fs_rename() syzbot reported a f2fs bug as below: BUG: memory leak unreferenced object 0xffff888127f70830 (size 16): comm "syz.0.23", pid 6144, jiffies 4294943712 hex dump (first 16 bytes): 3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff <.Wr[...n..3B9.. backtrace (crc 925f8a80): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4520 [inline] slab_alloc_node mm/slub.c:4844 [inline] __do_kmalloc_node mm/slub.c:5237 [inline] __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250 kmalloc_noprof include/linux/slab.h:954 [inline] fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364 f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143 f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961 f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308 vfs_rename+0x7ff/0x1250 fs/namei.c:6026 filename_renameat2+0x4f4/0x660 fs/namei.c:6144 __do_sys_renameat2 fs/namei.c:6173 [inline] __se_sys_renameat2 fs/namei.c:6168 [inline] __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in commit 40b2d55e0452 ("f2fs: fix to create selinux label during whiteout initialization"), we added a call to f2fs_setup_filename() without a matching call to f2fs_free_filename(), fix it.

References

NVD — CVE-2026-31714 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-31714
git.kernel.org/stable/c/047c0aef6a... WEB
https://git.kernel.org/stable/c/047c0aef6af37a2a35181aa085c616ad286386f1
git.kernel.org/stable/c/369eb2016d... WEB
https://git.kernel.org/stable/c/369eb2016d8e2f01931b3bad1cb9cefa83f44003
git.kernel.org/stable/c/3cf11e6f36... WEB
https://git.kernel.org/stable/c/3cf11e6f36c170050c12171dd6fd3142711478fc
git.kernel.org/stable/c/a76c1cad4e... WEB
https://git.kernel.org/stable/c/a76c1cad4e80a9802ef8048662255417e3ce5b79
git.kernel.org/stable/c/c78206dcb9... WEB
https://git.kernel.org/stable/c/c78206dcb912ab60b8ee3cbe8c48d749a9a12e1e

Frequently Asked Questions

What is CVE-2026-31714?
CVE-2026-31714 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-401: Missing Release of Memory after Effective Lifetime.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-31714?
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-31714?
CVE-2026-31714 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-31714?
CVE-2026-31714 is classified under CWE-401: Missing Release of Memory after Effective Lifetime (The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.).
How can I check Maven dependencies for CVE-2026-31714?
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-48wq-5h48-mwqq",
  "modified" : "2026-05-06T21:31:32Z",
  "published" : "2026-05-01T15:30:33Z",
  "aliases" : [ "CVE-2026-31714" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid memory leak in f2fs_rename()\n\nsyzbot reported a f2fs bug as below:\n\nBUG: memory leak\nunreferenced object 0xffff888127f70830 (size 16):\n  comm \"syz.0.23\", pid 6144, jiffies 4294943712\n  hex dump (first 16 bytes):\n    3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff  <.Wr[...n..3B9..\n  backtrace (crc 925f8a80):\n    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]\n    slab_post_alloc_hook mm/slub.c:4520 [inline]\n    slab_alloc_node mm/slub.c:4844 [inline]\n    __do_kmalloc_node mm/slub.c:5237 [inline]\n    __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250\n    kmalloc_noprof include/linux/slab.h:954 [inline]\n    fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364\n    f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143\n    f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961\n    f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308\n    vfs_rename+0x7ff/0x1250 fs/namei.c:6026\n    filename_renameat2+0x4f4/0x660 fs/namei.c:6144\n    __do_sys_renameat2 fs/namei.c:6173 [inline]\n    __se_sys_renameat2 fs/namei.c:6168 [inline]\n    __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168\n    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n    do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94\n    entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe root cause is in commit 40b2d55e0452 (\"f2fs: fix to create selinux\nlabel during whiteout initialization\"), we added a call to\nf2fs_setup_filename() without a matching call to f2fs_free_filename(),\nfix it.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-31714"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/047c0aef6af37a2a35181aa085c616ad286386f1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/369eb2016d8e2f01931b3bad1cb9cefa83f44003"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3cf11e6f36c170050c12171dd6fd3142711478fc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a76c1cad4e80a9802ef8048662255417e3ce5b79"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c78206dcb912ab60b8ee3cbe8c48d749a9a12e1e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-401" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-01T14:16:21Z"
  }
}