VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/fabiolb/fabio: vulnerability history, versions and safety

github.com/fabiolb/fabio is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from May 2025 to Oct 2026. 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 C1 M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/fabiolb/fabio vulnerabilities

Vulert verdict on github.com/fabiolb/fabio v1.8.0 i

Updated on 23 Oct 2026

Action needed: v1.8.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 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • 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 v1.8.0 — affected i
  • Vulnerabilities on record 4 over 1 year · 2 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Stars 7,347 i
  • OpenSSF scorecard 5/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/fabiolb/fabio, 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.8.1-0.20261005054344-5b4c42855443 05 Oct 2026 C1 U1 MIT Yes Details →
v1.8.1-0.20260924073645-d8c5a69ab500 24 Sep 2026 C1 U1 MIT Yes Details →
v1.8.1-0.20260918061004-d6bb65f4abec 18 Sep 2026 C1 U1 MIT Yes Details →
v1.8.1-0.20260909015405-2aad4553c7f9 09 Sep 2026 C1 U1 MIT Yes Details →
v1.8.0 09 Sep 2026 C1 U1 MIT Yes Details →
v1.7.4-0.20260904000638-66e463d11c9e 04 Sep 2026 C1 U1 MIT Yes Details →
v1.7.4-0.20260811005942-2456d96493f3 11 Aug 2026 C1 U1 MIT Yes Details →
v1.7.3 06 Aug 2026 C1 U1 MIT Yes Details →
v1.7.3-0.20260715022839-f8012e2a0bb8 15 Jul 2026 C1 U1 MIT Yes Details →
v1.7.3-0.20260708023605-f6d2f8b6838d 08 Jul 2026 C1 U1 MIT Yes Details →
v1.7.3-0.20260703004207-a9aadebe7622 03 Jul 2026 C1 U1 MIT Yes Details →
v1.7.2 03 Jul 2026 C1 U1 MIT Yes Details →
v1.7.2-0.20260610232623-c75f8a6fdc0e 10 Jun 2026 C1 U1 MIT Yes Details →
v1.7.1 27 Apr 2026 C1 U1 MIT Yes Details →
v1.7.1-0.20260325005740-8b44a7574606 25 Mar 2026 C1 U1 MIT Yes Details →
v1.7.0 25 Mar 2026 C1 U1 MIT Yes Details →
v1.6.11 09 Dec 2025 C1 U1 MIT Yes Details →
v1.6.11-0.20251209025006-8f728087beff 09 Dec 2025 C1 U1 MIT Yes Details →
v1.6.10 24 Nov 2025 C1 U1 MIT Yes Details →
v1.6.10-0.20251121071010-5afcb17c46ee 21 Nov 2025 C1 U1 MIT Yes Details →
v1.6.10-0.20251031223541-d82418a249db 31 Oct 2025 C1 U1 MIT Yes Details →
v1.6.9 16 Oct 2025 C1 U1 MIT Yes Details →
v1.6.9-0.20251002180312-d4a112c05cf9 02 Oct 2025 C1 U1 MIT Yes Details →
v1.6.8 23 Sep 2025 C1 U1 MIT Yes Details →
v1.6.8-0.20250819020218-d82583e12501 19 Aug 2025 C1 U1 MIT Yes Details →
v1.6.8-0.20250531111102-d026a3712246 31 May 2025 C1 U1 MIT Yes Details →
v1.6.8-0.20250530013115-9980a9f843ba 30 May 2025 C1 U1 MIT Yes Details →
v1.6.7 30 May 2025 C1 U1 MIT Yes Details →
v1.6.7-0.20250527001256-ae0cefb961ca 27 May 2025 C1 U1 MIT Yes Details →
v1.6.6 26 May 2025 C1 U1 MIT Yes Details →
v1.6.6-0.20250526231055-fdaf1e966162 26 May 2025 C1 U1 MIT Yes Details →
v1.6.5 28 Feb 2025 C1 U1 MIT Yes Details →
v1.6.5-0.20250114213248-5d113395f3d0 14 Jan 2025 C1 U1 MIT Yes Details →
v1.6.5-0.20241202003744-c2e0c362cb2f 02 Dec 2024 C1 U1 MIT Yes Details →
v1.6.4 27 Nov 2024 C1 U1 MIT Yes Details →
v1.6.4-0.20241127213929-33c876b3141c 27 Nov 2024 C1 U1 MIT Yes Details →
v1.6.4-0.20241126231947-040767f26432 26 Nov 2024 C1 U1 MIT Yes Details →
v1.6.4-0.20241018212432-d2d85040c677 18 Oct 2024 C1 U1 MIT Yes Details →
v1.6.4-0.20240916030637-b0a8432c3354 16 Sep 2024 C1 U1 MIT Yes Details →
v1.6.4-0.20240905022903-3e6d9bb33237 05 Sep 2024 C1 U1 MIT Yes Details →
v1.6.4-0.20221210051028-642e425cf664 10 Dec 2022 C1 U1 MIT Yes Details →
v1.6.3 09 Dec 2022 C1 U1 MIT Yes Details →
v1.6.3-0.20220920143939-0d173888dd55 20 Sep 2022 C1 U1 MIT Yes Details →
v1.6.3-0.20220913204709-43602bde1d4b 13 Sep 2022 C1 U1 MIT Yes Details →
v1.6.3-0.20220913193206-9eab23f1cd54 13 Sep 2022 C1 U1 MIT Yes Details →
v1.6.2 13 Sep 2022 C1 U1 MIT Yes Details →
v1.6.2-0.20220720012117-555ec6968b89 20 Jul 2022 C1 U1 MIT Yes Details →
v1.6.2-0.20220719152228-af2d36fcdda8 19 Jul 2022 C1 U1 MIT Yes Details →
v1.6.1 19 Jul 2022 C1 U1 MIT Yes Details →
v1.6.1-0.20220712170916-fe7b872d75ef 12 Jul 2022 C1 U1 MIT Yes Details →
v1.6.1-0.20220708231007-a262a4e5bd07 08 Jul 2022 C1 U1 MIT Yes Details →
v1.6.1-0.20220506221922-22e41e42c0cb 06 May 2022 C1 U1 MIT Yes Details →
v1.6.1-0.20220506193710-3677770ef5b0 06 May 2022 C1 U1 MIT Yes Details →
v1.6.1-0.20220411213413-d73417bb0d00 11 Apr 2022 C1 U1 MIT Yes Details →
v1.6.1-0.20220411194549-621deb51b9b0 11 Apr 2022 C1 U1 MIT Yes Details →
v1.6.0 11 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220411163736-dc3d78654dcd 11 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220411155729-8b1ba30c837d 11 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220411152144-8808fc4f1bc0 11 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220409225725-0dea90a20f8f 09 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220409001535-86b4ed0e8d04 09 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220408215326-44ee358fd180 08 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220408184250-7e672a527efd 08 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220405215139-e62dd194303e 05 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220405202442-4325538e255a 05 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20220405201336-2b9517dbf215 05 Apr 2022 C1 U1 MIT Yes Details →
v1.5.16-0.20210504141706-bf654ba0f4c9 04 May 2021 C1 U1 MIT Yes Details →
v1.5.16-0.20210430165430-d8c81f8aa089 30 Apr 2021 C1 U1 MIT Yes Details →
v1.5.16-0.20210223215822-81ed7aaf12ee 23 Feb 2021 C1 U1 MIT Yes Details →
v1.5.15 01 Dec 2020 C1 U1 MIT Yes Details →
v1.5.14-0.20200910002120-16b759d0f667 10 Sep 2020 C1 U1 MIT Yes Details →
v1.5.14 09 Sep 2020 C1 U1 MIT Yes Details →
v1.5.10-0.20200903032829-205ad55917e8 03 Sep 2020 C1 U1 MIT Yes Details →
v1.5.14-0.20200202234843-c034d4fae1d6 02 Feb 2020 C1 U1 MIT Yes Details →
v1.5.12-0.20200130194331-1c9dc1d36473 30 Jan 2020 C1 U1 MIT Yes Details →
v1.5.13 18 Nov 2019 C1 U1 MIT Yes Details →
v1.5.12 11 Oct 2019 C1 U1 MIT Yes Details →
v1.5.12-0.20190715133204-d165b14813e6 15 Jul 2019 C1 U1 MIT Yes Details →
v1.5.12-0.20190708183107-ea3a36552bd1 08 Jul 2019 C1 U1 MIT Yes Details →
v1.5.12-0.20190620142536-f4b4dce50058 20 Jun 2019 C1 U1 MIT Yes Details →
v1.5.12-0.20190424000845-b11536bd126a 24 Apr 2019 C1 U1 MIT Yes Details →
v1.5.12-0.20190423144628-dad14b9ee325 23 Apr 2019 C1 U1 MIT Yes Details →
v1.5.12-0.20190419180018-bdc036420bfc 19 Apr 2019 C1 U1 MIT Yes Details →
v1.5.11-wrong.0.20190321204903-ed27a84cf456 21 Mar 2019 C1 U1 MIT Yes Details →
v1.5.11-wrong.0.20190226000253-dd9ef7d5712a 26 Feb 2019 C1 U1 MIT Yes Details →
v1.5.11 25 Feb 2019 C1 U1 MIT Yes Details →
v1.5.11-wrong 25 Feb 2019 C1 U1 MIT Yes Details →
v1.5.1-0.20181210120227-5fb4039bf946 10 Dec 2018 C1 U1 MIT Yes Details →
v1.5.11-0.20181210120227-5fb4039bf946 10 Dec 2018 C1 U1 MIT Yes Details →
v1.5.10 25 Oct 2018 C1 U1 MIT Yes Details →
v1.5.10-0.20180911190949-c730093c5479 11 Sep 2018 C1 U1 MIT Yes Details →
v1.5.10-0.20180816203900-edca2134c862 16 Aug 2018 C1 U1 MIT Yes Details →
v1.5.9 16 May 2018 C1 U1 MIT Yes Details →
v1.5.8 18 Feb 2018 C1 U1 MIT Yes Details →
v1.5.7 06 Feb 2018 C1 U1 MIT Yes Details →
v1.5.6 05 Jan 2018 C1 U1 MIT Yes Details →
v1.5.5 20 Dec 2017 C1 U1 MIT Yes Details →
v1.5.4 10 Dec 2017 C1 U1 MIT Yes Details →
v1.5.3 03 Nov 2017 C1 U1 MIT Yes Details →
v1.5.2 24 Jul 2017 C1 U1 MIT Yes Details →
v1.5.1 06 Jul 2017 C1 U1 — Yes Details →
v1.5.0 07 Jun 2017 C1 U1 — Yes Details →
v1.4.4 08 May 2017 C1 U1 — Yes Details →
v1.4.3 24 Apr 2017 C1 U1 — Yes Details →
v1.4.2 10 Apr 2017 C1 U1 — Yes Details →
v1.4.1 04 Apr 2017 C1 U1 — Yes Details →
v1.3.9-0.20170323104913-851afff92e42 23 Mar 2017 C1 U1 — Yes Details →
v1.3.9-0.20170323104729-32e596338912 23 Mar 2017 C1 U1 — Yes Details →
v1.3.9-0.20170323104636-a410bdbd4ccb 23 Mar 2017 C1 U1 — Yes Details →
v1.3.8 14 Feb 2017 C1 U1 — Yes Details →
v1.3.7 19 Jan 2017 C1 U1 — Yes Details →
v1.3.6 17 Jan 2017 C1 U1 — Yes Details →
v1.3.5 30 Nov 2016 C1 U1 — Yes Details →
v1.3.4 28 Oct 2016 C1 U1 — Yes Details →
v1.3.3 12 Oct 2016 C1 U1 — Yes Details →
v1.3.2 11 Sep 2016 C1 U1 — Yes Details →
v1.3.1 09 Sep 2016 C1 U1 — Yes Details →
v1.2.1 25 Aug 2016 C1 U1 — Yes Details →
v1.1.6-0.20160713073513-2fe73d28381b 13 Jul 2016 C1 U1 — Yes Details →
v1.1.6-0.20160712194545-9976da6d1e09 12 Jul 2016 C1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/fabiolb/fabio

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48865: Fabio HTTP Header Manipulation Vulnerability 9.1 critical 1.6.6 29 May 2025
CVE-2026-62987: Fabio Incomplete Fix for Trust Headers Vulnerability 5.8 medium 1.7.2 22 Sep 2026
CVE-2025-48865: Custom Header Manipulation Vulnerability in Fabio N/A unrated 1.6.6 03 Jun 2025
CVE-2026-62987: Fabio Incomplete Fix for Trust Headers Vulnerability N/A unrated 1.7.2 01 Oct 2026

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/fabiolb/fabio

Is github.com/fabiolb/fabio safe to use?

Vulert records 4 vulnerabilities for github.com/fabiolb/fabio in Go: 1 critical, 0 high, 1 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/fabiolb/fabio's Vulert package health score?

Vulert scores github.com/fabiolb/fabio 79/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/fabiolb/fabio affected?

Yes. v1.8.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/fabiolb/fabio should I use?

v1.8.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/fabiolb/fabio have?

4 vulnerabilities are recorded for github.com/fabiolb/fabio in the Go ecosystem: 1 critical, 0 high, 1 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/fabiolb/fabio vulnerabilities disclosed?

2 vulnerabilities were recorded for github.com/fabiolb/fabio in the last 12 months, and the oldest entry in this database dates to 29 May 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/fabiolb/fabio 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/fabiolb/fabio for upcoming vulnerabilities?

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