← Search results
CVE-LINKED INVENTORY29 SECURITY RECORDS
anthropics
claude-code
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at claude-code, 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-55607 | 29 Jun 2026 | >= 2.1.38, < 2.1.163 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-46406 | 29 Jun 2026 | >= 2.1.59, < 2.1.128 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-54316 | 23 Jun 2026 | >= 0.2.54, < 2.1.163 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-44470 | 13 May 2026 | < 1.3834.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-44467 | 13 May 2026 | >= 1.2581.0, < 1.4304.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-40068 | 5 May 2026 | >= 2.1.63, < 2.1.84 | 2.1.84. | Update reference ↗ |
| CVE-2026-39861 | 21 Apr 2026 | < 2.1.64 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-35603 | 17 Apr 2026 | < 2.1.75 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33068 | 20 Mar 2026 | < 2.1.53 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25725 | 6 Feb 2026 | < 2.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25724 | 6 Feb 2026 | < 2.1.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25723 | 6 Feb 2026 | < 2.0.55 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25722 | 6 Feb 2026 | < 2.0.57 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24887 | 3 Feb 2026 | < 2.0.72 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24053 | 3 Feb 2026 | < 2.0.74 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24052 | 3 Feb 2026 | < 1.0.111 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-21852 | 21 Jan 2026 | < 2.0.65 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66032 | 3 Dec 2025 | < 1.0.93 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-64755 | 21 Nov 2025 | < 2.0.31 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-65099 | 19 Nov 2025 | < 1.0.39 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59829 | 3 Oct 2025 | < 1.0.120 | 1.0.120. | Update reference ↗ |
| CVE-2025-59536 | 3 Oct 2025 | < 1.0.111 | 1.0.111. | Update reference ↗ |
| CVE-2025-59828 | 24 Sep 2025 | < 1.0.39 | 1.0.39. | Update reference ↗ |
| CVE-2025-59041 | 10 Sep 2025 | < 1.0.105 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-58764 | 10 Sep 2025 | < 1.0.105 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-55284 | 16 Aug 2025 | < 1.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54794 | 5 Aug 2025 | < 0.2.111 | 0.2.111. | Update reference ↗ |
| CVE-2025-54795 | 5 Aug 2025 | < 1.0.20 | 1.0.20. | Update reference ↗ |
| CVE-2025-52882 | 24 Jun 2025 | >= 0.2.116 < 1.0.24 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.