frdel
Agent-Zero
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 agent-zero, 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-4308 | 17 Mar 2026 | 0.9.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-4307 | 17 Mar 2026 | 0.9.7-10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6166 | 17 Jun 2025 | 0.8.0; 0.8.1; 0.8.2; 0.8.3; 0.8.4 | 0.8.4.1 | Update reference ↗ |
| CVE-2025-3547 | 14 Apr 2025 | 0.8.1.2 | 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.