osv-2026-308
Vulnerability from osv_ossfuzz
Published
2026-02-25 00:19
Modified
2026-02-25 00:19
Summary
Heap-buffer-overflow in vcardstructured_new_from_string
Details

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

Crash type: Heap-buffer-overflow WRITE 8
Crash state:
vcardstructured_new_from_string
vcardparameter_set_value_from_string
_parse_vcard
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "c7bab3f44497eb126baa7c10429192ebd9acec91:0d3735426835aff0bd8151a0203e0720b157315f",
        "introduced_range": "79a5324fd751adaa6c2336a215ca0783d5f57f29:e6c4d276a1df6c73bd2bec2c53dd98e367126375"
      },
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libical",
        "purl": "pkg:generic/libical"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "00fc43fd2faaa5a3d0a667dbb56bd35ba758892d"
            },
            {
              "fixed": "0d3735426835aff0bd8151a0203e0720b157315f"
            }
          ],
          "repo": "https://github.com/libical/libical.git",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=486715154\n\n```\nCrash type: Heap-buffer-overflow WRITE 8\nCrash state:\nvcardstructured_new_from_string\nvcardparameter_set_value_from_string\n_parse_vcard\n```\n",
  "id": "OSV-2026-308",
  "modified": "2026-02-25T00:19:49.964188Z",
  "published": "2026-02-25T00:19:49.963815Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=486715154"
    }
  ],
  "schema_version": "1.7.3",
  "summary": "Heap-buffer-overflow in vcardstructured_new_from_string"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.