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

dgraph-io

dgraph

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 dgraph, 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-63637 6 Aug 2026 < 25.3.8 25.3.8. Update reference ↗
CVE-2026-44840 8 Jul 2026 < 25.3.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-54061 8 Jul 2026 < 25.3.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-41492 24 Apr 2026 < 25.3.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-41327 24 Apr 2026 < 25.3.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-41328 24 Apr 2026 < 25.3.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-40173 15 Apr 2026 < 25.3.2 25.3.2. Update reference ↗
CVE-2026-34976 6 Apr 2026 < 25.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-31135 17 May 2023 < 23.0.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. 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.