Vulnerability Database · Go · Package report
github.com/hashicorp/go-cty: vulnerability history, versions and safety
github.com/hashicorp/go-cty is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/hashicorp/go-cty v1.5.0 i
Updated on 23 Oct 2026
Good news: v1.5.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.5.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.5.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.5.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 3 i
- OpenSSF scorecard 3/10 i
- Last release 19 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/hashicorp/go-cty, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- v1.5.1-0.20260831135143-aebd643414a5 31 Aug 2026
- v1.5.1-0.20250519080439-f280817bfcef 19 May 2025
- v1.5.1-0.20250513122110-08b05919367d 13 May 2025
- v1.5.1-0.20250331125210-39789d23d145 31 Mar 2025
- v1.5.1-0.20250326124508-ca64fed5e3fd 26 Mar 2025
- v1.5.1-0.20250325230353-ce534d0f8f5c 25 Mar 2025
- v1.5.1-0.20250318154235-0fdcf0e9302d 18 Mar 2025
- v1.5.0 17 Mar 2025
- v1.4.2-0.20250317155238-f3d5407653c4 17 Mar 2025
- v1.4.2-0.20250306191100-08cd546fd9d6 06 Mar 2025
- v1.4.2-0.20250306174208-b56e5cfc2dec 06 Mar 2025
- v1.4.1 05 Mar 2025
- v1.4.1-0.20250305213621-92d5fa8689eb 05 Mar 2025
- v1.4.1-0.20250305211553-1ad7e61edb72 05 Mar 2025
- v1.4.1-0.20241127173709-a0325cb22c13 27 Nov 2024
- v1.4.1-0.20230406142738-80f5adfaa76a 06 Apr 2023
- v0.0.0-20200723130312-85980079f637 23 Jul 2020
- v1.0.1-0.20200723130312-85980079f637 23 Jul 2020
- v1.4.1-0.20200723130312-85980079f637 23 Jul 2020
- v1.4.1-0.20200723130157-ab81b0bb19eb 23 Jul 2020
- v1.4.1-0.20200723130041-318abdb82609 23 Jul 2020
- v1.4.1-0.20200723130041-7da524df555f 23 Jul 2020
- v1.4.1-0.20200723130041-893893e8d227 23 Jul 2020
- v0.0.0-20200414143053-d3edf31b6320 14 Apr 2020
- v1.0.1-0.20200414143053-d3edf31b6320 14 Apr 2020
- v1.2.1-0.20200414143053-d3edf31b6320 14 Apr 2020
- v1.4.1-0.20200414143053-d3edf31b6320 14 Apr 2020
- v1.4.1-0.20200414002455-7acc001e5424 14 Apr 2020
- v0.0.0-20180302160414-49fa5e03c418 02 Mar 2018
- v0.0.0-20170618161233-43e36090bc5f 18 Jun 2017
All 30 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for github.com/hashicorp/go-cty
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About github.com/hashicorp/go-cty
Is github.com/hashicorp/go-cty safe to use?
Vulert has no vulnerabilities on record for github.com/hashicorp/go-cty in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/hashicorp/go-cty's Vulert package health score?
Vulert scores github.com/hashicorp/go-cty 58/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of github.com/hashicorp/go-cty affected?
No. v1.5.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/hashicorp/go-cty should I use?
v1.5.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does github.com/hashicorp/go-cty have?
0 vulnerabilities are recorded for github.com/hashicorp/go-cty in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new github.com/hashicorp/go-cty vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hashicorp/go-cty in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of github.com/hashicorp/go-cty are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor github.com/hashicorp/go-cty for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hashicorp/go-cty version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.