VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/hashicorp-forge/hermes: vulnerability history, versions and safety

github.com/hashicorp-forge/hermes is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 48 releases, from Feb 2025 to Mar 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/hashicorp-forge/hermes vulnerabilities

Vulert verdict on github.com/hashicorp-forge/hermes v0.5.0 i

Updated on 23 Oct 2026

Action needed: v0.5.0 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 81/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.5.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 03 Mar 2025 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Stars 1,909 i
  • Last release 20 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-forge/hermes, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.5.1-0.20260327112705-d18e2109be93 27 Mar 2026 H1 U1 MPL-2.0 Yes Details →
v0.5.0 14 Feb 2025 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20250212214755-e36d47961609 12 Feb 2025 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20250212214755-e36d47961609 12 Feb 2025 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240604220328-ced8f53c5fb4 04 Jun 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240415172943-e44e932d2db9 15 Apr 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240404005714-497877253335 04 Apr 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240404001012-69b4d2e606db 04 Apr 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240318235424-3f52210b4837 18 Mar 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240222221630-1543f36f02eb 22 Feb 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240222000731-c499fd5e2b76 22 Feb 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240220181928-b800a7ed4fa7 20 Feb 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240131212701-72b3a94c1e7e 31 Jan 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.1-0.20240131004112-25fa3dc02671 31 Jan 2024 H1 U1 MPL-2.0 Yes Details →
v0.4.0 19 Jan 2024 H1 U1 MPL-2.0 Yes Details →
v0.3.1-0.20240112214344-4fe455f5c2ae 12 Jan 2024 H1 U1 MPL-2.0 Yes Details →
v0.3.1-0.20231220175325-1dc162b16969 20 Dec 2023 H1 U1 MPL-2.0 Yes Details →
v0.3.1-0.20230825205310-282626a77b2e 25 Aug 2023 H1 U1 MPL-2.0 Yes Details →
v0.3.1-0.20230825204004-c2a875ab6e6c 25 Aug 2023 H1 U1 MPL-2.0 Yes Details →
v0.3.1-0.20230823184930-5b45c5e2c0bc 23 Aug 2023 H1 U1 MPL-2.0 Yes Details →
v0.3.0 17 Aug 2023 H1 U1 MPL-2.0 Yes Details →
v0.2.1-0.20230616182106-a67228fc6508 16 Jun 2023 H1 U1 MPL-2.0 Yes Details →
v0.2.0 16 Jun 2023 H1 U1 MPL-2.0 Yes Details →
v0.1.0 05 May 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230502191135-5cab61811464 02 May 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230405204129-82e6c2a95360 05 Apr 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230404232918-ebe142a30f2f 04 Apr 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230403175829-1e7f511e8f27 03 Apr 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230331131754-b42949ebb427 31 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230329202602-143329555401 29 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230325003859-1a968d405fb7 25 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230323224058-89341c931874 23 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230302022706-b95416fbcc4a 02 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230301031330-2e6c67223a66 01 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230301001135-99356cb0b7f8 01 Mar 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230224034040-3e122005a6c4 24 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230215224819-7e0088e584f2 15 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.2-0.20230210231418-6dc2f0f2b8b3 10 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.1 09 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230206195535-dcc5b5e681b0 06 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230206153636-53b0abc8a47c 06 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230204015623-694c5b920be4 04 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230203220059-631585dd8967 03 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230203215128-152e29ec7485 03 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230203204224-ef1b593c321a 03 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230203013148-39040b7c390c 03 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230201184432-2277f911a37f 01 Feb 2023 H1 U1 MPL-2.0 Yes Details →
v0.0.0-20230131165933-29325824d654 31 Jan 2023 H1 U1 MPL-2.0 Yes Details →

All 48 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/hashicorp-forge/hermes

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-1293: Hermes Package Authentication Bypass Due to Improper JWT Validation 8.2 high 0.5.0 20 Feb 2025
JWT Validation Flaw in Hermes Package - GO-2025-3475 N/A unrated 0.5.0 03 Mar 2025

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/hashicorp-forge/hermes

Is github.com/hashicorp-forge/hermes safe to use?

Vulert records 2 vulnerabilities for github.com/hashicorp-forge/hermes in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/hashicorp-forge/hermes's Vulert package health score?

Vulert scores github.com/hashicorp-forge/hermes 81/100, which reads as in good shape. 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-forge/hermes affected?

Yes. v0.5.0, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/hashicorp-forge/hermes should I use?

v0.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-forge/hermes have?

2 vulnerabilities are recorded for github.com/hashicorp-forge/hermes in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 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-forge/hermes vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/hashicorp-forge/hermes in the last 12 months, and the oldest entry in this database dates to 20 Feb 2025. 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-forge/hermes 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-forge/hermes for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hashicorp-forge/hermes version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.