osv-2026-565
Vulnerability from osv_ossfuzz
Published
2026-04-12 00:05
Modified
2026-04-12 00:05
Summary
Heap-buffer-overflow in xmlFAParsePosCharGroup
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
xmlFAParsePosCharGroup
xmlFAParseCharGroup
xmlFAParseCharGroup
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libxml2",
        "purl": "pkg:generic/libxml2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "07b13346cb7421090545bfb29f58bcbef8d36261"
            },
            {
              "fixed": "a7511af09f99995cdf81994db21f4eba564276b5"
            },
            {
              "introduced": "d1bccc480fd00b40c86ac26d3f3b6c91c46d18f7"
            }
          ],
          "repo": "https://gitlab.gnome.org/GNOME/libxml2.git",
          "type": "GIT"
        }
      ],
      "versions": [
        "v2.15.3"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=501547873\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\nxmlFAParsePosCharGroup\nxmlFAParseCharGroup\nxmlFAParseCharGroup\n```\n",
  "id": "OSV-2026-565",
  "modified": "2026-04-12T00:05:45.925675Z",
  "published": "2026-04-12T00:05:45.925380Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=501547873"
    }
  ],
  "schema_version": "1.7.5",
  "summary": "Heap-buffer-overflow in xmlFAParsePosCharGroup"
}


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.