Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY16 SECURITY RECORDS

protobufjs

protobuf.js

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at protobuf.js, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-59876 8 Jul 2026 >= 8.2.0, < 8.6.5 8.6.5. Update reference ↗
CVE-2026-59877 8 Jul 2026 >= 7.5.0, < 7.6.5; >= 8.0.0, < 8.6.6 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-54269 22 Jun 2026 < 7.6.3; >= 8.0.0, < 8.6.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48712 22 Jun 2026 < 7.6.1; >= 8.0.0, < 8.4.1 For more about Red Hat Developer Hub, see References links Update reference ↗
CVE-2026-54270 22 Jun 2026 >=8.2.0, < 8.5.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-44295 13 May 2026 >= 2.0.0, < 2.0.2; < 1.2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42290 13 May 2026 >= 2.0.0, < 2.0.2; < 1.2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-45740 13 May 2026 < 7.5.8; >= 8.0.0, < 8.2.0 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-44294 13 May 2026 < 7.5.6; >= 8.0.0, < 8.0.2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-44293 13 May 2026 protobuf.js: < 7.5.6, >= 8.0.0, < 8.0.2 RHSA-2026:34160: Red Hat Ansible Automation Platform 2.6 for RHEL 9 Update reference ↗
CVE-2026-44292 13 May 2026 < 7.5.6; >= 8.0.0, < 8.0.2 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-44291 13 May 2026 < 7.5.6; >= 8.0.0, < 8.0.2 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-44290 13 May 2026 < 7.5.6; >= 8.0.0, < 8.0.2 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-44289 13 May 2026 < 7.5.6; >= 8.0.0, < 8.0.2 For more about Ansible plugins for Red Hat Developer Hub, see References links Update reference ↗
CVE-2026-44288 13 May 2026 < 7.5.6; >= 8.0.0, < 8.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-41242 18 Apr 2026 protobuf.js: < 7.5.5, >= 8.0.0-experimental, < 8.0.1 RHSA-2026:21338: Red Hat Developer Hub 1.8 Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.