CVE-2026-89479: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-2f22-4vgf-p33p
Share
CVSS 9.8
Published
Advisory Summary

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

CVE-2026-89479 at a Glance

CVE Identifier CVE-2026-89479
GHSA Identifier GHSA-2f22-4vgf-p33p
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification General Security Weakness
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-89479

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-89479, 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: sctp: stop processing a packet once its association is deleted sctp_endpoint_bh_rcv() looks the association up only when chunk->asoc is NULL, and caches the result in chunk->asoc and chunk->transport without taking a reference. A packet that matches no association is handed to the endpoint, so a peer can bundle COOKIE ECHO, SHUTDOWN and SHUTDOWN ACK in one packet. The COOKIE ECHO creates the association, the SHUTDOWN chunk caches it, and with the outqueue empty the SHUTDOWN ACK reaches sctp_sf_do_9_2_final(), so the association and its transports are freed. The endpoint loop has no counterpart to the asoc->base.dead check in sctp_assoc_bh_rcv(). The next chunk writes to last_time_heard in the freed transport and is then passed to sctp_do_sm() with the freed association. The transport is freed through RCU, so this needs the packet to come off the socket backlog, where the loop runs in task context. The endpoint loop cannot do the same check: it holds no reference on the association, so reading asoc->base.dead would itself be a use-after-free. Mark the packet for discard in the command interpreter, just before it deletes the association. That is also before sctp_inq_free() releases the chunk on the association receive path. sctp_sf_do_5_2_4_dupcook() issues SCTP_CMD_DELETE_TCB for the temporary association, while the one the packet belongs to stays alive. A restarting peer can bundle DATA behind its COOKIE ECHO, so compare against chunk->asoc and leave that case alone.

References

NVD — CVE-2026-89479 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89479
git.kernel.org/stable/c/09c3b193a3... WEB
https://git.kernel.org/stable/c/09c3b193a3e8fe53e1f416e2f8e3283d2a785405
git.kernel.org/stable/c/47e15a8d12... WEB
https://git.kernel.org/stable/c/47e15a8d12e366d0d261bcbc394394f44418938d
git.kernel.org/stable/c/5c0b2dbbda... WEB
https://git.kernel.org/stable/c/5c0b2dbbdafc9eeeb11fffe1e46551fc3b55d8ee
git.kernel.org/stable/c/7d970353ee... WEB
https://git.kernel.org/stable/c/7d970353eeb98f46a3b9dc602850e4f6336a9889
git.kernel.org/stable/c/a713e1b3a2... WEB
https://git.kernel.org/stable/c/a713e1b3a265f180ad25a08e17be15d67a2f7149
git.kernel.org/stable/c/ed85fe91a6... WEB
https://git.kernel.org/stable/c/ed85fe91a61bc0e0da6b585c07102b20f4cc65a0
git.kernel.org/stable/c/ee3f04cf56... WEB
https://git.kernel.org/stable/c/ee3f04cf566f6041aa9a0360494fd8db5ade383a
git.kernel.org/stable/c/fa306a40e7... WEB
https://git.kernel.org/stable/c/fa306a40e716c5abcd967475459ce1ebd56e5115

Frequently Asked Questions

What is CVE-2026-89479?
CVE-2026-89479 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-89479?
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-89479?
CVE-2026-89479 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-89479?
CVE-2026-89479 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89479?
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-2f22-4vgf-p33p",
  "modified" : "2026-09-14T15:32:26Z",
  "published" : "2026-09-11T21:31:28Z",
  "aliases" : [ "CVE-2026-89479" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: stop processing a packet once its association is deleted\n\nsctp_endpoint_bh_rcv() looks the association up only when chunk->asoc is\nNULL, and caches the result in chunk->asoc and chunk->transport without\ntaking a reference.\n\nA packet that matches no association is handed to the endpoint, so a peer\ncan bundle COOKIE ECHO, SHUTDOWN and SHUTDOWN ACK in one packet. The\nCOOKIE ECHO creates the association, the SHUTDOWN chunk caches it, and\nwith the outqueue empty the SHUTDOWN ACK reaches sctp_sf_do_9_2_final(),\nso the association and its transports are freed.\n\nThe endpoint loop has no counterpart to the asoc->base.dead check in\nsctp_assoc_bh_rcv(). The next chunk writes to last_time_heard in the freed\ntransport and is then passed to sctp_do_sm() with the freed association.\nThe transport is freed through RCU, so this needs the packet to come off\nthe socket backlog, where the loop runs in task context.\n\nThe endpoint loop cannot do the same check: it holds no reference on the\nassociation, so reading asoc->base.dead would itself be a use-after-free.\nMark the packet for discard in the command interpreter, just before it\ndeletes the association. That is also before sctp_inq_free() releases the\nchunk on the association receive path.\n\nsctp_sf_do_5_2_4_dupcook() issues SCTP_CMD_DELETE_TCB for the temporary\nassociation, while the one the packet belongs to stays alive. A restarting\npeer can bundle DATA behind its COOKIE ECHO, so compare against\nchunk->asoc and leave that case alone.",
  "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-89479"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/09c3b193a3e8fe53e1f416e2f8e3283d2a785405"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/47e15a8d12e366d0d261bcbc394394f44418938d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5c0b2dbbdafc9eeeb11fffe1e46551fc3b55d8ee"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d970353eeb98f46a3b9dc602850e4f6336a9889"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a713e1b3a265f180ad25a08e17be15d67a2f7149"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ed85fe91a61bc0e0da6b585c07102b20f4cc65a0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ee3f04cf566f6041aa9a0360494fd8db5ade383a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fa306a40e716c5abcd967475459ce1ebd56e5115"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:29Z"
  }
}