{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "0"
                  },
                  {
                    "fixed": "1.4.4"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StringRangeExpression"
              },
              {
                "range": [
                  {
                    "introduced": "0"
                  },
                  {
                    "fixed": "1.5.1"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StringRangeExpression"
              }
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3ecb65cf56111fc8dd8429a25ff515763fbc74fe"
            },
            {
              "fixed": "3a74c74a8139526e34da32c6cc41ed7c71aaded5"
            }
          ],
          "repo": "https://github.com/bacnet-stack/bacnet-stack",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-v3gx-mwrp-xvh5"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-121"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45265.json"
  },
  "details": "BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.4 and 1.5.1, there is a stack-based out-of-bounds write / stack-buffer-overflow in bacnet-stack when the server processes a malicious Atomic-Read-File request in record access mode. The bug is triggered on the real server side. A crafted request can set an excessively large RecordCount, which is later used as the loop bound for writing record data into a stack-allocated BACNET_ATOMIC_READ_FILE_DATA data structure. However, the stack object only has space for one fileData element. When the loop reaches i = 1, the code computes \u0026data-\u003efileData[1], which is already out of bounds, and the resulting invalid pointer is passed down to memmove(), causing a stack-buffer-overflow. This issue has been patched in versions 1.4.4 and 1.5.1.",
  "id": "CVE-2026-45265",
  "modified": "2026-11-14T02:30:37.869890196Z",
  "published": "2026-11-12T19:59:55.457Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45265.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-v3gx-mwrp-xvh5"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45265"
    },
    {
      "type": "FIX",
      "url": "https://github.com/bacnet-stack/bacnet-stack/pull/1340"
    }
  ],
  "schema_version": "1.9.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Atomic-Read-File RecordCount Stack-Based Out-of-Bounds Write in bacnet-stack"
}