osv-2026-917
Vulnerability from osv_ossfuzz
Published
2026-06-15 00:19
Modified
2026-06-15 00:19
Summary
Heap-buffer-overflow in ixheaace_process
Details

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=523531852

Crash type: Heap-buffer-overflow WRITE {*}
Crash state:
ixheaace_process
xaac_enc_fuzzer.cpp
References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "9428b5860dd83dbd2c5b5cc5bf3915abfefbad21:b9193197055e1e87f841f73c1a3fbca796b2da09",
        "introduced_range": "388435c8f8f43fe0e44bf0d31dd3965283f119ec:eb62778aee21a98b9f6f5c27e0a1f2546a175172"
      },
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libxaac",
        "purl": "pkg:generic/libxaac"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "fb6a68848a05401a1aba5747d29595cd344faa40"
            },
            {
              "fixed": "b9193197055e1e87f841f73c1a3fbca796b2da09"
            }
          ],
          "repo": "https://github.com/ittiam-systems/libxaac.git",
          "type": "GIT"
        }
      ],
      "versions": [
        "v0.1.13"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=523531852\n\n```\nCrash type: Heap-buffer-overflow WRITE {*}\nCrash state:\nixheaace_process\nxaac_enc_fuzzer.cpp\n```\n",
  "id": "OSV-2026-917",
  "modified": "2026-06-15T00:19:37.594771Z",
  "published": "2026-06-15T00:19:37.594492Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=523531852"
    }
  ],
  "schema_version": "1.7.5",
  "summary": "Heap-buffer-overflow in ixheaace_process"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.