osv-2026-741
Vulnerability from osv_ossfuzz
Published
2026-05-16 00:05
Modified
2026-05-16 00:05
Summary
Heap-buffer-overflow in p11_lexer_next
Details

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

Crash type: Heap-buffer-overflow READ 2
Crash state:
p11_lexer_next
conf_fuzzer.c
References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "3822b6b2de2e606809afeaffae7ffdc682447261:c5d5130c6610760151e61df9fede4826f765e7ef",
        "introduced_range": "511230aa9f11fca3e8186a24d93406151e21d415:24151187c977bd10b30fffedc47033b438a15c87"
      },
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "p11-kit",
        "purl": "pkg:generic/p11-kit"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "c6bf6d6d88140f43f4c8f9367cad7b72f79e1105"
            },
            {
              "fixed": "c5d5130c6610760151e61df9fede4826f765e7ef"
            }
          ],
          "repo": "https://github.com/p11-glue/p11-kit.git",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=513100838\n\n```\nCrash type: Heap-buffer-overflow READ 2\nCrash state:\np11_lexer_next\nconf_fuzzer.c\n```\n",
  "id": "OSV-2026-741",
  "modified": "2026-05-16T00:05:41.607646Z",
  "published": "2026-05-16T00:05:41.607233Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=513100838"
    }
  ],
  "schema_version": "1.7.5",
  "summary": "Heap-buffer-overflow in p11_lexer_next"
}


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.