Vulnerability Database · Go · Package report
github.com/hashicorp/go-secure-stdlib/fileutil: vulnerability history, versions and safety
github.com/hashicorp/go-secure-stdlib/fileutil 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.
See all github.com/hashicorp/go-secure-stdlib/fileutil vulnerabilities
Vulert verdict on github.com/hashicorp/go-secure-stdlib/fileutil v0.1.0 i
Updated on 23 Oct 2026
Good news: v0.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Quiet
What to do: Stay on v0.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 74 i
- OpenSSF scorecard 4/10 i
- Last release 53 months ago i
- Licence MPL-2.0 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-secure-stdlib/fileutil, 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.
- v0.1.1-0.20261005181433-49bfb1561b96 05 Oct 2026
- v0.1.1-0.20241126042323-48acf6924f6c 26 Nov 2024
- v0.1.1-0.20240801143802-fab9dfbe9dbc 01 Aug 2024
- v0.1.1-0.20240319184836-90fcdf1d959f 19 Mar 2024
- v0.1.1-0.20240213021721-e24d50507acc 13 Feb 2024
- v0.1.1-0.20231122172001-b4a7f3e5652c 22 Nov 2023
- v0.1.1-0.20231030181425-07759ea3feec 30 Oct 2023
- v0.1.1-0.20230719171342-72fcd87cb5f9 19 Jul 2023
- v0.1.1-0.20230606170242-1a4b95565d57 06 Jun 2023
- v0.1.1-0.20230529201716-91e78a9970b4 29 May 2023
- v0.1.1-0.20230529185512-e7535ed29617 29 May 2023
- v0.1.1-0.20221206213606-4db62e808f6c 06 Dec 2022
- v0.1.1-0.20221130175209-f7789ac19a1f 30 Nov 2022
- v0.1.1-0.20221122211730-f52ba9532e2c 22 Nov 2022
- v0.0.0-20220427223102-17e9a8f06103 27 Apr 2022
- v0.1.0 27 Apr 2022
- v0.0.0-20220418165313-7c52bacc6b2f 18 Apr 2022
- v0.0.0-20220414165337-0f14a493710e 14 Apr 2022
- v0.0.0-20220414045134-ff5feca1443a 14 Apr 2022
All 19 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-secure-stdlib/fileutil
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-secure-stdlib/fileutil
Is github.com/hashicorp/go-secure-stdlib/fileutil safe to use?
Vulert has no vulnerabilities on record for github.com/hashicorp/go-secure-stdlib/fileutil 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-secure-stdlib/fileutil's Vulert package health score?
Vulert scores github.com/hashicorp/go-secure-stdlib/fileutil 54/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-secure-stdlib/fileutil affected?
No. v0.1.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-secure-stdlib/fileutil should I use?
v0.1.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-secure-stdlib/fileutil have?
0 vulnerabilities are recorded for github.com/hashicorp/go-secure-stdlib/fileutil 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-secure-stdlib/fileutil vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hashicorp/go-secure-stdlib/fileutil 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-secure-stdlib/fileutil 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-secure-stdlib/fileutil for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hashicorp/go-secure-stdlib/fileutil version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.