CVE-2026-80800: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-8pjc-rhhp-w5xq
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80800
GHSA Identifier GHSA-8pjc-rhhp-w5xq
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-80800

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-80800, 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: nfc: llcp: bound the connect_sn TLV walk to the skb Commit 27256cdb290e ("nfc: llcp: bound SNL TLV parsing to the skb and add length checks") fixed the unbounded TLV walk in nfc_llcp_recv_snl(), and commit d8bd2dedbde5 ("nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers") subsequently bounded nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv(). One sibling parser sharing the same pattern remains unbounded: nfc_llcp_connect_sn(). nfc_llcp_connect_sn() walks a TLV list, reading a two-byte header (type, length) followed by length bytes of value, without checking that the two header bytes or the declared length stay within the buffer. It returns a pointer to a service name of up to 255 bytes that may point past the end of the skb; it is subsequently consumed by memcmp() in nfc_llcp_sock_from_sn(). In addition tlv_array_len was computed as "skb->len - LLCP_HEADER_SIZE" in size_t, so a CONNECT/CC frame shorter than the LLCP header underflows to a huge length and the walk runs far past the buffer. nfc_llcp_connect_sn() is reachable from nfc_llcp_recv_connect() and nfc_llcp_recv_cc(), i.e. from received CONNECT and CC PDUs. A nearby NFC device can reach this without authentication; LLCP link activation happens automatically after NFC-DEP, and the nfc_llcp_rx_skb() dispatcher applies no minimum-length guard. Walk the TLV list by pointer, bounded by skb_tail_pointer(skb), and validate each declared length before use, matching the approach already used for nfc_llcp_recv_snl(). Starting the walk at &skb->data[LLCP_HEADER_SIZE] against the tail pointer also removes the size_t underflow for short frames. Found by 0sec automated security-research tooling (https://0sec.ai).

References

NVD — CVE-2026-80800 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80800
git.kernel.org/stable/c/0cfbdb0e13... WEB
https://git.kernel.org/stable/c/0cfbdb0e13ab5b0765d77f96af67eb879cbc9736
git.kernel.org/stable/c/1964addc8d... WEB
https://git.kernel.org/stable/c/1964addc8dd535a05d5d3b55b4d1ac19ae31aa65
git.kernel.org/stable/c/22e5177ba1... WEB
https://git.kernel.org/stable/c/22e5177ba1196a0b272a6a46c2575eb940a939c4
git.kernel.org/stable/c/389986fd79... WEB
https://git.kernel.org/stable/c/389986fd79e4d43f971a03b512645a1bb63c982f
git.kernel.org/stable/c/55c68ac93e... WEB
https://git.kernel.org/stable/c/55c68ac93e7dacc0f5f608b9c39dd4ff48cf28e8
git.kernel.org/stable/c/65a0ec7783... WEB
https://git.kernel.org/stable/c/65a0ec7783b06068dda6745dd689bf4a91ee64aa
git.kernel.org/stable/c/b2ebdfe3d5... WEB
https://git.kernel.org/stable/c/b2ebdfe3d5b76e91f267a61cbc3f9a0e3f77071e
git.kernel.org/stable/c/e18d044bab... WEB
https://git.kernel.org/stable/c/e18d044bab6d3d0280639098c3fe6621692cbfe2
git.kernel.org/stable/c/e87527b506... WEB
https://git.kernel.org/stable/c/e87527b506c40db9af528714b7b1240918eb80fc

Frequently Asked Questions

What is CVE-2026-80800?
CVE-2026-80800 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-80800?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80800?
CVE-2026-80800 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80800?
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-8pjc-rhhp-w5xq",
  "modified" : "2026-09-04T18:31:26Z",
  "published" : "2026-09-04T18:31:26Z",
  "aliases" : [ "CVE-2026-80800" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: llcp: bound the connect_sn TLV walk to the skb\n\nCommit 27256cdb290e (\"nfc: llcp: bound SNL TLV parsing to the skb and\nadd length checks\") fixed the unbounded TLV walk in nfc_llcp_recv_snl(),\nand commit d8bd2dedbde5 (\"nfc: llcp: fix OOB read and u8 offset wrap in\nTLV parsers\") subsequently bounded nfc_llcp_parse_gb_tlv() and\nnfc_llcp_parse_connection_tlv(). One sibling parser sharing the same\npattern remains unbounded: nfc_llcp_connect_sn().\n\nnfc_llcp_connect_sn() walks a TLV list, reading a two-byte header\n(type, length) followed by length bytes of value, without checking that\nthe two header bytes or the declared length stay within the buffer. It\nreturns a pointer to a service name of up to 255 bytes that may point\npast the end of the skb; it is subsequently consumed by memcmp() in\nnfc_llcp_sock_from_sn(). In addition tlv_array_len was computed as\n\"skb->len - LLCP_HEADER_SIZE\" in size_t, so a CONNECT/CC frame shorter\nthan the LLCP header underflows to a huge length and the walk runs far\npast the buffer.\n\nnfc_llcp_connect_sn() is reachable from nfc_llcp_recv_connect() and\nnfc_llcp_recv_cc(), i.e. from received CONNECT and CC PDUs. A nearby\nNFC device can reach this without authentication; LLCP link activation\nhappens automatically after NFC-DEP, and the nfc_llcp_rx_skb()\ndispatcher applies no minimum-length guard.\n\nWalk the TLV list by pointer, bounded by skb_tail_pointer(skb), and\nvalidate each declared length before use, matching the approach already\nused for nfc_llcp_recv_snl(). Starting the walk at\n&skb->data[LLCP_HEADER_SIZE] against the tail pointer also removes the\nsize_t underflow for short frames.\n\nFound by 0sec automated security-research tooling (https://0sec.ai).",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80800"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0cfbdb0e13ab5b0765d77f96af67eb879cbc9736"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1964addc8dd535a05d5d3b55b4d1ac19ae31aa65"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/22e5177ba1196a0b272a6a46c2575eb940a939c4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/389986fd79e4d43f971a03b512645a1bb63c982f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/55c68ac93e7dacc0f5f608b9c39dd4ff48cf28e8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/65a0ec7783b06068dda6745dd689bf4a91ee64aa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b2ebdfe3d5b76e91f267a61cbc3f9a0e3f77071e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e18d044bab6d3d0280639098c3fe6621692cbfe2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e87527b506c40db9af528714b7b1240918eb80fc"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-04T16:18:06Z"
  }
}