VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

fortio.org/proxy: vulnerability history, versions and safety

fortio.org/proxy is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Jan 2023 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
2 vulnerabilities recorded M1 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 fortio.org/proxy vulnerabilities

Vulert verdict on fortio.org/proxy v1.32.0 i

Updated on 23 Oct 2026

Good news: v1.32.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 73/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v1.32.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.32.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.32.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 20 Aug 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 23 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 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 fortio.org/proxy, 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.32.0 11 Oct 2026 none Apache-2.0 — Details →
v1.31.2 11 Jun 2026 none Apache-2.0 — Details →
v1.31.1 06 Jun 2026 none Apache-2.0 — Details →
v1.30.0 06 Mar 2026 none Apache-2.0 — Details →
v1.29.5 16 Feb 2026 none Apache-2.0 — Details →
v1.29.4 15 Feb 2026 none Apache-2.0 — Details →
v1.29.3 26 Jan 2026 none Apache-2.0 — Details →
v1.29.3-0.20260126170309-e64174431b60 26 Jan 2026 none Apache-2.0 — Details →
v1.29.3-0.20260126170027-d86a8234e46a 26 Jan 2026 none Apache-2.0 — Details →
v1.29.2 17 Jan 2026 none Apache-2.0 — Details →
v1.29.1 23 Dec 2025 none Apache-2.0 — Details →
v1.29.0 12 Oct 2025 none Apache-2.0 — Details →
v1.28.1 12 Sep 2025 none Apache-2.0 — Details →
v1.28.0 12 Sep 2025 none Apache-2.0 — Details →
v1.27.2-0.20250826233122-68fb92f3ac82 26 Aug 2025 none Apache-2.0 — Details →
v1.27.1 19 Aug 2025 none Apache-2.0 — Details →
v1.27.0 08 Aug 2025 none Apache-2.0 — Details →
v1.26.0 08 Aug 2025 none Apache-2.0 — Details →
v1.25.5 25 May 2025 none Apache-2.0 — Details →
v1.25.4 21 Apr 2025 none Apache-2.0 — Details →
v1.25.3 18 Apr 2025 none Apache-2.0 — Details →
v1.25.2 15 Apr 2025 none Apache-2.0 — Details →
v1.25.1 08 Apr 2025 none Apache-2.0 — Details →
v1.25.0 04 Apr 2025 none Apache-2.0 — Details →
v1.24.2 02 Apr 2025 none Apache-2.0 — Details →
v1.24.1 25 Mar 2025 none Apache-2.0 — Details →
v1.24.1-0.20250325223056-86ceacb282fb 25 Mar 2025 none Apache-2.0 — Details →
v1.24.0 25 Mar 2025 none Apache-2.0 — Details →
v1.23.0 24 Mar 2025 none Apache-2.0 — Details →
v1.22.1-0.20250324230726-3e7a82a6b1e7 24 Mar 2025 none Apache-2.0 — Details →
v1.22.0 24 Mar 2025 none Apache-2.0 — Details →
v1.21.2-0.20250323023924-b253814a7777 23 Mar 2025 none Apache-2.0 — Details →
v1.21.1 18 Mar 2025 none Apache-2.0 — Details →
v1.20.8-0.20241113000903-3b0b27bfb2af 13 Nov 2024 none Apache-2.0 — Details →
v1.21.0 13 Nov 2024 none Apache-2.0 — Details →
v1.20.8-0.20241108063412-26a735dce577 08 Nov 2024 none Apache-2.0 — Details →
v1.20.8-0.20241007135914-abcf0609efad 07 Oct 2024 none Apache-2.0 — Details →
v1.20.7 04 Oct 2024 none Apache-2.0 — Details →
v1.20.7-0.20241004003233-00cf49f51dab 04 Oct 2024 none Apache-2.0 — Details →
v1.20.6 27 Sep 2024 none Apache-2.0 — Details →
v1.20.6-0.20240927034017-268cce9f67a7 27 Sep 2024 none Apache-2.0 — Details →
v1.20.5 19 Sep 2024 none Apache-2.0 — Details →
v1.20.5-0.20240919201456-d71fb5a0b0f3 19 Sep 2024 none Apache-2.0 — Details →
v1.20.3-0.20240917193130-cfe8e03df589 17 Sep 2024 none Apache-2.0 — Details →
v1.20.4 17 Sep 2024 none Apache-2.0 — Details →
v1.20.2 06 Sep 2024 none Apache-2.0 — Details →
v1.20.2-0.20240906170434-3b60772598c9 06 Sep 2024 none Apache-2.0 — Details →
v1.20.2-0.20240816045500-82610b52cc8d 16 Aug 2024 none Apache-2.0 — Details →
v1.20.1 07 Aug 2024 none Apache-2.0 — Details →
v1.20.1-0.20240807164353-35a34e5a49a8 07 Aug 2024 none Apache-2.0 — Details →
v1.19.9-0.20240703165317-9af7181f7c7d 03 Jul 2024 none Apache-2.0 — Details →
v1.20.0 03 Jul 2024 none Apache-2.0 — Details →
v1.19.8 06 Jun 2024 none Apache-2.0 — Details →
v1.19.8-0.20240606074429-f0e318e80637 06 Jun 2024 none Apache-2.0 — Details →
v1.19.7 01 Jun 2024 none Apache-2.0 — Details →
v1.19.7-0.20240601021355-0699e9d993da 01 Jun 2024 none Apache-2.0 — Details →
v1.19.6 21 May 2024 none Apache-2.0 — Details →
v1.19.6-0.20240521235605-a70f37bed4d9 21 May 2024 none Apache-2.0 — Details →
v1.19.5 03 Apr 2024 none Apache-2.0 — Details →
v1.19.4 23 Mar 2024 none Apache-2.0 — Details →
v1.19.4-0.20240323152723-6c49b822d7fa 23 Mar 2024 none Apache-2.0 — Details →
v1.19.3 06 Mar 2024 none Apache-2.0 — Details →
v1.19.3-0.20240306152315-72f286c591eb 06 Mar 2024 none Apache-2.0 — Details →
v1.19.2 11 Feb 2024 none Apache-2.0 — Details →
v1.19.2-0.20240211195553-327adc81d985 11 Feb 2024 none Apache-2.0 — Details →
v1.19.1 20 Dec 2023 none Apache-2.0 — Details →
v1.19.1-0.20231220033057-ac810811b0ed 20 Dec 2023 none Apache-2.0 — Details →
v1.18.2-0.20231209020010-6540b10bc536 09 Dec 2023 none Apache-2.0 — Details →
v1.19.0 09 Dec 2023 none Apache-2.0 — Details →
v1.18.1 22 Nov 2023 none Apache-2.0 — Details →
v1.18.1-0.20231122073605-3d5c08df2a83 22 Nov 2023 none Apache-2.0 — Details →
v1.18.0 22 Nov 2023 none Apache-2.0 — Details →
v1.16.4-0.20231115225807-1b54e835be7f 15 Nov 2023 none Apache-2.0 — Details →
v1.17.0 15 Nov 2023 none Apache-2.0 — Details →
v1.16.3 11 Oct 2023 none Apache-2.0 — Details →
v1.16.2 14 Sep 2023 none Apache-2.0 — Details →
v1.16.2-0.20230914004203-df4995b0e54d 14 Sep 2023 none Apache-2.0 — Details →
v1.16.1 04 Aug 2023 none Apache-2.0 — Details →
v1.16.1-0.20230804163441-ca978033dcda 04 Aug 2023 none Apache-2.0 — Details →
v1.16.0 04 Aug 2023 none Apache-2.0 — Details →
v1.15.6-0.20230804013020-6c733577822d 04 Aug 2023 none Apache-2.0 — Details →
v1.16.0-pre1 04 Aug 2023 none Apache-2.0 — Details →
v1.15.5 03 Aug 2023 none Apache-2.0 — Details →
v1.15.4 25 Jul 2023 none Apache-2.0 — Details →
v1.15.3 12 Jul 2023 none Apache-2.0 — Details →
v1.15.2 12 Jul 2023 none Apache-2.0 — Details →
v1.15.1 12 Jul 2023 none Apache-2.0 — Details →
v1.15.0 07 Jul 2023 none Apache-2.0 — Details →
v1.14.3-0.20230707143402-73f4e7f51f70 07 Jul 2023 none Apache-2.0 — Details →
v1.14.2 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-0.20230629215039-160d03f2c271 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-pre2.0.20230629214521-408671a6d5f3 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-pre3 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-pre1.0.20230629213925-bf5c3f080d84 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-pre2 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-0.20230629213619-17efcec266fc 29 Jun 2023 none Apache-2.0 — Details →
v1.14.2-pre1 29 Jun 2023 none Apache-2.0 — Details →
v1.14.1 29 Jun 2023 none Apache-2.0 — Details →
v1.13.2-0.20230615194612-002b74445ba7 15 Jun 2023 none Apache-2.0 — Details →
v1.14.0 15 Jun 2023 none Apache-2.0 — Details →
v1.13.1 07 May 2023 none — — Details →
v1.13.0 01 May 2023 none — — Details →
v1.12.3-0.20230430032035-cf0fc895ed2b 30 Apr 2023 none — — Details →
v1.13.0-pre1 30 Apr 2023 none — — Details →
v1.12.3-0.20230430031723-813d28ee1350 30 Apr 2023 none — — Details →
v1.12.2 06 Apr 2023 none — — Details →
v1.12.1 09 Mar 2023 none — — Details →
v1.12.0 05 Mar 2023 none — — Details →
v1.11.1 26 Feb 2023 none — — Details →
v1.11.0 26 Feb 2023 none — — Details →
v1.10.4 20 Feb 2023 none — — Details →
v1.10.3 19 Feb 2023 none — — Details →
v1.10.2 19 Feb 2023 none — — Details →
v1.10.1 19 Feb 2023 none — — Details →
v1.10.0 19 Feb 2023 none — — Details →
v1.9.1 17 Feb 2023 none — — Details →
v1.9.0 17 Feb 2023 none — — Details →
v1.8.1 03 Feb 2023 none — — Details →
v1.8.0 28 Jan 2023 none — — Details →
v1.7.0 28 Jan 2023 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1

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 fortio.org/proxy

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Information Leakage and Denial of Service in fortio.org/proxy N/A medium 1.6.1 27 Jan 2023
Initial debug-host handler implementation could leak information and facilitate denial of service in fortio.org/proxy N/A unrated 1.6.1 20 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 fortio.org/proxy

Is fortio.org/proxy safe to use?

Vulert records 2 vulnerabilities for fortio.org/proxy in Go: 0 critical, 0 high, 1 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 fortio.org/proxy's Vulert package health score?

Vulert scores fortio.org/proxy 73/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 fortio.org/proxy affected?

No. v1.32.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 fortio.org/proxy should I use?

v1.32.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 fortio.org/proxy have?

2 vulnerabilities are recorded for fortio.org/proxy in the Go ecosystem: 0 critical, 0 high, 1 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 fortio.org/proxy vulnerabilities disclosed?

0 vulnerabilities were recorded for fortio.org/proxy in the last 12 months, and the oldest entry in this database dates to 27 Jan 2023. 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 fortio.org/proxy 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 fortio.org/proxy for upcoming vulnerabilities?

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