{
  "@id": "urn:uuid:ce50994c-6860-4a84-8c5c-61429102a9a3",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-09-24T09:31:26.931840+00:00",
  "statements": [
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2018-3738 is fixed in version 1.5.1-tuxcare.1 of protobufjs.",
      "vulnerability": {
        "name": "CVE-2018-3738"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41242 is fixed in version 1.5.1-tuxcare.1 of protobufjs.",
      "vulnerability": {
        "name": "CVE-2026-41242"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44288 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44288. The vulnerable code (protobufjs's minimal UTF-8 decoder in lib/utf8/index.js or src/util/utf8.js) does not exist in this version. Version 1.5.1 uses a completely different architecture, delegating all UTF-8 encoding/decoding operations to the ByteBuffer.js library (v~2.0) via methods like readVString(). The minimal UTF-8 decoder that contains the...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-44288"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44288. The vulnerable code (protobufjs's minimal UTF-8 decoder in lib/utf8/index.js or src/util/utf8.js) does not exist in this version. Version 1.5.1 uses a completely different architecture, delegating all UTF-8 encoding/decoding operations to the ByteBuffer.js library (v~2.0) via methods like readVString(). The minimal UTF-8 decoder that contains the..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44289 is fixed in version 1.5.1-tuxcare.1 of protobufjs.",
      "vulnerability": {
        "name": "CVE-2026-44289"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44290 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44290. The vulnerability requires option path traversal features (setParsedOption, parsedOptions) present in modern protobufjs versions 6.x/7.x but absent in this 2013-era version. Version 1.5.1 has a fundamentally different architecture and does not parse or traverse dotted option paths.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-44290"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44290. The vulnerability requires option path traversal features (setParsedOption, parsedOptions) present in modern protobufjs versions 6.x/7.x but absent in this 2013-era version. Version 1.5.1 has a fundamentally different architecture and does not parse or traverse dotted option paths."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44291 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44291. While this version uses plain objects for type lookups and does not have the specific protections added in the upstream patch (Object.create(null), __proto__ filtering), it employs a fundamentally different architecture with comprehensive regex validation that acts as an alternative defense, preventing polluted prototype properties from enabling ...",
      "vulnerability": {
        "name": "CVE-2026-44291"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44291. While this version uses plain objects for type lookups and does not have the specific protections added in the upstream patch (Object.create(null), __proto__ filtering), it employs a fundamentally different architecture with comprehensive regex validation that acts as an alternative defense, preventing polluted prototype properties from enabling ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44292 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44292. While it processes plain JavaScript objects with properties, the reflection-based architecture provides an alternative defense that prevents __proto__ injection. The init function validates all property keys against the message schema via the set method, which rejects unknown keys including __proto__ before any assignment occurs.",
      "vulnerability": {
        "name": "CVE-2026-44292"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-44292. While it processes plain JavaScript objects with properties, the reflection-based architecture provides an alternative defense that prevents __proto__ injection. The init function validates all property keys against the message schema via the set method, which rejects unknown keys including __proto__ before any assignment occurs."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44293 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Target version 1.5.1 is not affected by CVE-2026-44293. The vulnerability exists in protobuf.js v7.x's code generation for toObject conversion when processing JSON descriptors with malicious bytes field defaults. Version 1.5.1 uses a completely different architecture: it only accepts .proto text files (not JSON descriptors) and uses runtime reflection instead of code generation. The vulnerable ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-44293"
      },
      "impact_statement": "not_affected \u2014 Target version 1.5.1 is not affected by CVE-2026-44293. The vulnerability exists in protobuf.js v7.x's code generation for toObject conversion when processing JSON descriptors with malicious bytes field defaults. Version 1.5.1 uses a completely different architecture: it only accepts .proto text files (not JSON descriptors) and uses runtime reflection instead of code generation. The vulnerable ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-44294 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 of protobufjs is not affected by CVE-2026-44294. This CVE concerns a code generation vulnerability in modern protobuf.js (7.x/8.x) where field names containing control characters are embedded into statically generated JavaScript code without proper escaping, causing syntax errors. Version 1.5.1 uses a completely different architecture: (1) it validates all field/message/enum names...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-44294"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 of protobufjs is not affected by CVE-2026-44294. This CVE concerns a code generation vulnerability in modern protobuf.js (7.x/8.x) where field names containing control characters are embedded into statically generated JavaScript code without proper escaping, causing syntax errors. Version 1.5.1 uses a completely different architecture: (1) it validates all field/message/enum names..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-45740 is fixed in version 1.5.1-tuxcare.1 of protobufjs.",
      "vulnerability": {
        "name": "CVE-2026-45740"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-48712 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 CVE-2026-48712 targets unbounded recursion in toObject() JSON conversion and google.protobuf.Any wrapper functions specific to protobuf.js 6.x/7.x architecture. The target repository (protobufjs version 1.5.1) uses a fundamentally different architecture that lacks these conversion mechanisms entirely. Version 1.5.1 only supports binary protobuf encoding/decoding without any JSON or plain object...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-48712"
      },
      "impact_statement": "not_affected \u2014 CVE-2026-48712 targets unbounded recursion in toObject() JSON conversion and google.protobuf.Any wrapper functions specific to protobuf.js 6.x/7.x architecture. The target repository (protobufjs version 1.5.1) uses a fundamentally different architecture that lacks these conversion mechanisms entirely. Version 1.5.1 only supports binary protobuf encoding/decoding without any JSON or plain object..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-54269 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 protobufjs 1.5.1 uses a fundamentally different architecture from the vulnerable protobufjs 8.5.0. The vulnerability patterns described in CVE-2026-54269 (hasOwnProperty shadowing, rpcCall shadowing, and $-prefixed name collisions) do not exist in the legacy 1.x codebase.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-54269"
      },
      "impact_statement": "not_affected \u2014 protobufjs 1.5.1 uses a fundamentally different architecture from the vulnerable protobufjs 8.5.0. The vulnerability patterns described in CVE-2026-54269 (hasOwnProperty shadowing, rpcCall shadowing, and $-prefixed name collisions) do not exist in the legacy 1.x codebase."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-54270 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 does not implement the vulnerable feature. The CVE states 'protobufjs 8.2.0 added support for preserving unknown fields' - this feature was introduced years after version 1.5.1 was released. The target's decode logic discards unknown fields by design (Reflect.js:754-773), preventing the memory accumulation vulnerability. This behavior is semantically equivalent to the fix (discard...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-54270"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 does not implement the vulnerable feature. The CVE states 'protobufjs 8.2.0 added support for preserving unknown fields' - this feature was introduced years after version 1.5.1 was released. The target's decode logic discards unknown fields by design (Reflect.js:754-773), preventing the memory accumulation vulnerability. This behavior is semantically equivalent to the fix (discard..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59876 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-59876. The vulnerability targets the protobufjs Text Format extension (ext/textformat.js) and proto3 map fields, both of which were introduced in version 6.x+ (circa 2016). Version 1.5.1 (released 2013) predates proto3, has no ext/ directory, no text format extension, and no map field support. The vulnerable code path does not exist in this version.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-59876"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 is not affected by CVE-2026-59876. The vulnerability targets the protobufjs Text Format extension (ext/textformat.js) and proto3 map fields, both of which were introduced in version 6.x+ (circa 2016). Version 1.5.1 (released 2013) predates proto3, has no ext/ directory, no text format extension, and no map field support. The vulnerable code path does not exist in this version."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/protobufjs@1.5.1-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/protobufjs@1.5.1-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-59877 does not affect version 1.5.1-tuxcare.1 of protobufjs. not_affected \u2014 Version 1.5.1 does not contain the vulnerable code pattern described in CVE-2026-59877. The infinite loop vulnerability was introduced in later versions (6.x+) when option parsing was refactored to use a while loop. Version 1.5.1 uses a different architecture with sequential token advancement and immediate validation.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-59877"
      },
      "impact_statement": "not_affected \u2014 Version 1.5.1 does not contain the vulnerable code pattern described in CVE-2026-59877. The infinite loop vulnerability was introduced in later versions (6.x+) when option parsing was refactored to use a while loop. Version 1.5.1 uses a different architecture with sequential token advancement and immediate validation."
    }
  ]
}