VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/stripe/smokescreen is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from Apr 2022 to Aug 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 M2 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.

See all github.com/stripe/smokescreen vulnerabilities

Vulert verdict on github.com/stripe/smokescreen v0.1.0 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • 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.1.0 — affected i
  • Vulnerabilities on record 4 over 2 years · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS 5.8 i
  • With no published fix 0 i
  • Stars 1,366 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month 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/stripe/smokescreen, 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.1.1-0.20261022111441-68e7b8218e22 22 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261022084026-f1e79feb24d5 22 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261016132015-bc3bf31dc7eb 16 Oct 2026 M2 U2 MIT Yes Details →
v0.0.0-20261012101009-7d0ddfa75899 12 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261012101009-7d0ddfa75899 12 Oct 2026 M2 U2 MIT Yes Details →
v0.0.0-20261010145826-8e963a32d4b0 10 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261010145826-8e963a32d4b0 10 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261007141246-99be9f595dc6 07 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261006190356-d533c7aa3eb3 06 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261006122040-ac3ca0904680 06 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261006094618-17508c01599d 06 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261005185801-1f0d5a0748ff 05 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261005131930-49c55fa67308 05 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261001184347-a061a16965cd 01 Oct 2026 M2 U2 MIT Yes Details →
v0.0.0-20261001085937-fa5bb56b48fe 01 Oct 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20261001085937-fa5bb56b48fe 01 Oct 2026 M2 U2 MIT Yes Details →
v0.0.0-20260930090433-0ac0a3bac34e 30 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260930090433-0ac0a3bac34e 30 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260930085203-ba6624ab95d5 30 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260930031808-530e59a31c44 30 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260929094455-2d9dad869df8 29 Sep 2026 M2 U2 MIT Yes Details →
v0.0.0-20260928104106-6c4469888782 28 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260928104106-6c4469888782 28 Sep 2026 M2 U2 MIT Yes Details →
v0.0.0-20260925102505-c8bfe28c88f5 25 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260925102505-c8bfe28c88f5 25 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260924213847-4dff4a2b9c28 24 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260924073014-9622eeeb5b0a 24 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260923144644-68b149e52d5f 23 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260923121553-ede63db17688 23 Sep 2026 M2 U2 MIT Yes Details →
v0.1.1-0.20260922194512-2376b6dff8fe 22 Sep 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260918150203-609eb8931420 18 Sep 2026 M2 U2 MIT Yes Details →
v0.1.0 18 Sep 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260918134635-d3a7c693c2a0 18 Sep 2026 M2 U2 MIT Yes Details →
v0.0.0-20260909080646-82f05bfded58 09 Sep 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260909080646-82f05bfded58 09 Sep 2026 M2 U2 MIT Yes Details →
v0.0.0-20260828121251-d4da883a6714 28 Aug 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260828121251-d4da883a6714 28 Aug 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260819101244-f03c477dc9f4 19 Aug 2026 M2 U2 MIT Yes Details →
v0.0.0-20260803132036-131fba29ce1e 03 Aug 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260803132036-131fba29ce1e 03 Aug 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260729084022-da4840c9d873 29 Jul 2026 M2 U2 MIT Yes Details →
v0.0.0-20260706062719-a3294a6cc4e4 06 Jul 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260706062719-a3294a6cc4e4 06 Jul 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260701072857-9cace3f02f51 01 Jul 2026 M2 U2 MIT Yes Details →
v0.0.0-20260409081830-7d45971c8968 09 Apr 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260409081830-7d45971c8968 09 Apr 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260217125948-464b1115f802 17 Feb 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20260109122431-eae81044dc83 09 Jan 2026 M2 U2 MIT Yes Details →
v0.0.5-0.20251218091603-a7fdfcb5b930 18 Dec 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251203135059-9b8d021bb4fd 03 Dec 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251124142651-acdeb9067928 24 Nov 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251104063955-8e2eca634f7e 04 Nov 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251029161736-d0ac78902fde 29 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251028163907-45a7aaaf2008 28 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251028042146-896802e35c83 28 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251027105422-9aef7a9c2324 27 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251016054837-3ec99c08f3a4 16 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251010075746-de6f27c17e18 10 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251007091445-0382217c7e71 07 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20251002132831-b361f18f47dd 02 Oct 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250924071708-5de34de7ae7e 24 Sep 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250916093149-a19a48b6cc0e 16 Sep 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250916063829-7ae7a27acd93 16 Sep 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250915055232-ba3c79cd28eb 15 Sep 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250909104520-bd5f1e5a1d15 09 Sep 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250908060439-20d23c2e0ba6 08 Sep 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250828094203-b2ad55a6ac47 28 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250827133120-50693bc5224b 27 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250819052102-9093d2807fde 19 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250818135248-70ed8880a723 18 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250818073014-4e5636fa1c70 18 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250814180023-c84a02fef77b 14 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250814122158-6022d2e3d941 14 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250811085319-566d471a48a5 11 Aug 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250730040932-e5be1ce1d73f 30 Jul 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250729061912-d5e523a786cf 29 Jul 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250728045348-08fc04569093 28 Jul 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250725083650-c8543abd512f 25 Jul 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250724053007-00e240ce1eda 24 Jul 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250710054731-31eeeabfa14c 10 Jul 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250625125230-48d10534761c 25 Jun 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250624200256-5992e0532a2b 24 Jun 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250520143514-1b618edf4d3d 20 May 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20250516062519-69e4506ca247 16 May 2025 M2 U2 MIT Yes Details →
v0.0.5-0.20241104220037-bffe947fa6f6 04 Nov 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20241023062616-523d9278201b 23 Oct 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20241017112949-9556eb95409a 17 Oct 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20241011070416-688e70be7822 11 Oct 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20241010145604-c75cffbae9c2 10 Oct 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20241008092207-f6f8191dd005 08 Oct 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240917215859-dab4bdeb9878 17 Sep 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240904210319-149b19db8177 04 Sep 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240711223113-85c4c64e1e01 11 Jul 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240711173855-f0e29cc25472 11 Jul 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240702232902-c347cc9353bf 02 Jul 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240621210351-08e2921cbf9b 21 Jun 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240423131719-eb1ac09e96e9 23 Apr 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240313221623-970bc4db5a43 13 Mar 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240216213956-065ad0e4c549 16 Feb 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240215211339-fbd1ea77df19 15 Feb 2024 M2 U2 MIT Yes Details →
v0.0.5-0.20240215154536-24ee0c8790d6 15 Feb 2024 M2 U2 — Yes Details →
v0.0.5-0.20231206184233-a6241de61940 06 Dec 2023 M2 U2 — Yes Details →
v0.0.5-0.20231201193234-8c0fa26edf63 01 Dec 2023 M2 U2 — Yes Details →
v0.0.5-0.20231115174026-4cae3b1723ee 15 Nov 2023 M2 U2 — Yes Details →
v0.0.5-0.20231114044248-413045a5db40 14 Nov 2023 M2 U2 — Yes Details →
v0.0.5-0.20231108190155-997578a19ae8 08 Nov 2023 M2 U2 — Yes Details →
v0.0.5-0.20230804201041-6b9e46bd7e95 04 Aug 2023 M2 U2 — Yes Details →
v0.0.5-0.20230804194253-0a8a02741dd1 04 Aug 2023 M2 U2 — Yes Details →
v0.0.5-0.20230804163547-c86310d7000d 04 Aug 2023 M2 U2 — Yes Details →
v0.0.5-0.20230727141912-14a7af2d8f79 27 Jul 2023 M2 U2 — Yes Details →
v0.0.5-0.20230713132135-81a59fdf0b38 13 Jul 2023 M2 U2 — Yes Details →
v0.0.5-0.20230712205358-4ed00069777b 12 Jul 2023 M2 U2 — Yes Details →
v0.0.5-0.20230623161238-604044bb2308 23 Jun 2023 M2 U2 — Yes Details →
v0.0.0-20230531165139-8dd3072b71df 31 May 2023 M2 U2 — Yes Details →
v0.0.5-0.20230531165139-8dd3072b71df 31 May 2023 M2 U2 — Yes Details →
v0.0.5-0.20230519125647-65b5bdb241a8 19 May 2023 M2 U2 — Yes Details →
v0.0.5-0.20230414132506-7c83effc9df4 14 Apr 2023 M2 U2 — Yes Details →
v0.0.5-0.20230222191641-83ed067e3423 22 Feb 2023 M2 U2 — Yes Details →
v0.0.5-0.20221212223417-ddf0b612eb69 12 Dec 2022 M2 U2 — Yes Details →
v0.0.0-20221201205256-4835f355a9d3 01 Dec 2022 M2 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 2

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/smokescreen

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-24825: Smokescreen SSRF via deny list bypass 5.8 medium 0.0.3 07 Apr 2022
CVE-2022-29188: Smokescreen SSRF via deny list bypass (square brackets) 5.3 medium 0.0.4 24 May 2022
Smokescreen SSRF via deny list bypass in github.com/stripe/smokescreen N/A unrated 0.0.3 21 Aug 2024
Smokescreen SSRF via deny list bypass in github.com/stripe/smokescreen N/A unrated 0.0.4 21 Aug 2024

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/smokescreen

Is github.com/stripe/smokescreen safe to use?

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

Vulert scores github.com/stripe/smokescreen 85/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/smokescreen affected?

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

Which version of github.com/stripe/smokescreen 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/stripe/smokescreen have?

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

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

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