Vulnerability Database · Go · Package report

github.com/stripe/stripe-cli: vulnerability history, versions and safety

github.com/stripe/stripe-cli is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from Mar 2022 to Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 L1 U2
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.

Vulert verdict on github.com/stripe/stripe-cli v1.55.0 i

Updated on 23 Oct 2026

Action needed: v1.55.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 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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 v1.55.0 — affected i
  • Vulnerabilities on record 4 over 2 years · 0 in the last year i
  • Latest disclosure 06 Sep 2024 i
  • Highest CVSS 7.7 i
  • With no published fix 0 i
  • Stars 2,208 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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/stripe/stripe-cli, 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
v1.55.1-0.20261021233901-4501fc5a6e58 21 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.55.0 21 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.54.1 19 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.2-0.20261015203142-7839c312a40e 15 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.54.0 15 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.2-0.20261013202244-f2a0bf3f4b44 13 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.2-0.20261009005800-66ddb49f8122 09 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.1 07 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.1-0.20261005170753-514ac7e5bc8a 05 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.1-0.20261002211755-42b9689fc7bc 02 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.53.0 30 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.52.2 30 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.52.1 29 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.52.1-0.20260925232814-56ce423582b1 25 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.52.0 24 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.51.1 21 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.51.1-0.20260919001800-afbfd857a2ba 19 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.51.0 17 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.12-0.20260911233708-5de1df22230d 11 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.12-0.20260910171352-334e5f138f2a 10 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.11 09 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.11-0.20260904222436-3c465797a8d0 04 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.11-0.20260902225432-53747866af9d 02 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.11-0.20260902211920-2e9c1af4dfa9 02 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.10 02 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.9 02 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.9-0.20260901213752-7cbaba7dbea5 01 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.8 01 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.7 01 Sep 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.6 26 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.5 21 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.5-0.20260821205311-f5f390bc3729 21 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.5-0.20260821201218-c0c026ef9ef6 21 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.4 21 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.4-0.20260819205508-fb8dc0a5461c 19 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.3 19 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.2 19 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.1 14 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.1-0.20260813203128-02cbe03b3948 13 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.4 13 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.50.0 13 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.3 13 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.2 06 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.2-0.20260804211404-5b91d59a4114 04 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.1 04 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.1-0.20260731173700-c2377215f141 31 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.45.0 30 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.44.1 28 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.44.1-0.20260724202742-142fe5410330 24 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20260720230326-b91704db4838 20 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.44.1-0.20260720230326-b91704db4838 20 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20260720164722-a9c134dc761c 20 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.44.0 20 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20260718174634-b437c31f2147 18 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.9-0.20260718174634-b437c31f2147 18 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.8 13 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.8-0.20260709212444-44488cb6ef1e 09 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.7 09 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.6 02 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.5 02 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.4 01 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.3 01 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.3-0.20260630221317-ee314b4c38ff 30 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.2 24 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.1 24 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.43.0 24 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20260622201557-62327e2b491a 22 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.15 22 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.15-0.20260622201557-62327e2b491a 22 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.14 18 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.13 12 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.12 12 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.11 10 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.10 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.7 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.8 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.9 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.6 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.5 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.4 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.3 09 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.2 05 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20260528183307-9e0aa035244d 28 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.1 28 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.41.3-0.20260522224207-f6c6986fb42a 22 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.42.0 22 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.41.2 20 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.41.2-0.20260519234635-77d0ae046bc1 19 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.41.0 14 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.41.1 14 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.9 27 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.8 24 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.7 21 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.6 15 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.4 13 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.5 13 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.4-0.20260408212110-5872f76400de 08 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.3 08 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.1 07 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.2 07 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.40.1-0.20260403213903-e8426adac9e3 03 Apr 2026 H1 U1 — Yes Details →
v1.40.1-0.20260401192120-9be32db90164 01 Apr 2026 H1 U1 — Yes Details →
v1.40.0 30 Mar 2026 H1 U1 — Yes Details →
v1.39.0 26 Mar 2026 H1 U1 — Yes Details →
v1.38.3 24 Mar 2026 H1 U1 — Yes Details →
v1.38.2 23 Mar 2026 H1 U1 — Yes Details →
v1.38.1 21 Mar 2026 H1 U1 — Yes Details →
v1.38.0 20 Mar 2026 H1 U1 — Yes Details →
v1.37.8 18 Mar 2026 H1 U1 — Yes Details →
v1.37.7 17 Mar 2026 H1 U1 — Yes Details →
v1.37.6 17 Mar 2026 H1 U1 — Yes Details →
v1.37.5 17 Mar 2026 H1 U1 — Yes Details →
v1.37.4 17 Mar 2026 H1 U1 — Yes Details →
v1.37.3 11 Mar 2026 H1 U1 — Yes Details →
v1.37.2 02 Mar 2026 H1 U1 — Yes Details →
v1.37.1 25 Feb 2026 H1 U1 — Yes Details →
v1.36.1-0.20260225184308-53eeeb2266a4 25 Feb 2026 H1 U1 — Yes Details →
v1.37.0 25 Feb 2026 H1 U1 — Yes Details →
v1.35.1 17 Feb 2026 H1 U1 — Yes Details →
v1.35.0 28 Jan 2026 H1 U1 — Yes Details →

The newest 120 of 726 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/stripe/stripe-cli

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →

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/stripe/stripe-cli

Is github.com/stripe/stripe-cli safe to use?

Vulert records 4 vulnerabilities for github.com/stripe/stripe-cli in Go: 0 critical, 1 high, 0 medium and 1 low, plus 2 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/stripe/stripe-cli's Vulert package health score?

Vulert scores github.com/stripe/stripe-cli 88/100, which reads as healthy. 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/stripe/stripe-cli affected?

Yes. v1.55.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.

How many vulnerabilities does github.com/stripe/stripe-cli have?

4 vulnerabilities are recorded for github.com/stripe/stripe-cli in the Go ecosystem: 0 critical, 1 high, 0 medium and 1 low, plus 2 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/stripe/stripe-cli vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/stripe/stripe-cli in the last 12 months, and the oldest entry in this database dates to 10 Mar 2022. 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/stripe/stripe-cli 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/stripe/stripe-cli for upcoming vulnerabilities?

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