HashiCorp
Tooling
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 tooling, 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-87993 | 10 Sep 2026 | 0.27.2 < 0.43.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-8715 | 13 Aug 2026 | 1.3.0 < 1.5.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16326 | 29 Jul 2026 | 0.1.0 < 0.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16328 | 29 Jul 2026 | 0.1.0 < 0.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16498 | 28 Jul 2026 | 0.3.0 < 1.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16496 | 28 Jul 2026 | 0.3.0 < 1.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-14869 | 28 Jul 2026 | 0.3.0 < 1.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-14361 | 8 Jul 2026 | 0.1.0 < 0.42.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-5061 | 12 May 2026 | 0.1.0 < 0.42.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-4660 | 9 Apr 2026 | < 1.8.6 | Red Hat Trusted Artifact Signer simplifies cryptographic signing and verifying of software artifacts such as container images, binaries and source code changes. It is a self-managed on-premise deployment of the Sigstore project available at https://sigstore.dev Platform Engineers, Software Developers and Security Professionals may use RHTAS to ensure the integrity, transparency and assurance of their organization's software supply chain. For details on using the operator, refer to the product documentation at https://access.redhat.com/documentation/en-us/red_hat_trusted_artifact_signer/1.3 You can find the release notes for this version of Red Hat Trusted Artifact Signer at https://access.redhat.com/documentation/en-us/red_hat_trusted_artifact_signer/1.3/html-single/release_notes/index | Update reference ↗ |
| CVE-2025-13357 | 21 Nov 2025 | 4.2.0 < 5.5.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1293 | 20 Feb 2025 | < 0.5.0 | 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.