Vulnerability Database · Go · Package report

github.com/ulikunitz/xz: vulnerability history, versions and safety

github.com/ulikunitz/xz is a package in the Go ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Apr 2021 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 M1 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/ulikunitz/xz v0.5.17 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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.17 — affected i
  • Vulnerabilities on record 5 over 4 years · 0 in the last year i
  • Latest disclosure 17 Sep 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 561 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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/ulikunitz/xz, 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.17 19 Sep 2026 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.16 20 Jul 2026 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.16-0.20260706184924-54af70c67419 06 Jul 2026 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-last-dev 15 Oct 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.16-0.20250831072111-b37104025432 31 Aug 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.16-0.20250830093319-cdbb6ac101f9 30 Aug 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.15 29 Aug 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.14 28 Aug 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.14-rc.1 21 Aug 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.13 20 Aug 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.3.0.20250227202934-03d8b7c53fdb 27 Feb 2025 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.3.0.20240921101250-d42d4b51cd8d 21 Sep 2024 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.3.0.20240816175954-1cfff80b8aaf 16 Aug 2024 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.3.0.20240501181208-1e8b7722f248 01 May 2024 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20240403185035-4f11dce79b99 03 Apr 2024 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.12 03 Apr 2024 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.3 12 Jun 2023 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.2 10 Jun 2023 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha.1 30 Apr 2023 H2 M1 U2 BSD-3-Clause Yes Details →
v0.6.0-alpha1 30 Apr 2023 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20221213191206-f56ebbfaa240 13 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.12-0.20221213191206-f56ebbfaa240 13 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11 12 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20221210183537-0b7c695d23f8 10 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20221210183537-0b7c695d23f8 10 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20221209230222-553507794087 09 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20221209224707-886dc9acde19 09 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20221207211040-3b140e2f0868 07 Dec 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20220506054203-e4c082767ae8 06 May 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20220413104901-f8f287becd00 13 Apr 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20220313062410-d605bc0b245d 13 Mar 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20220101152630-dfe81c322212 01 Jan 2022 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20211230161555-fb74d75e34da 30 Dec 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20211217155726-ae233692d6d4 17 Dec 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20211217155726-ae233692d6d4 17 Dec 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20211217155014-057ed3994928 17 Dec 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20211209072742-cebda213290c 09 Dec 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20210221104125-d2624c667fd5 21 Feb 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20210205010328-fdaf408660c3 05 Feb 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.11-0.20210205010006-060c89d64f5e 05 Feb 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20210202193614-b0e6b5a2af12 02 Feb 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.10 02 Feb 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.10-0.20210202191906-51328d47e206 02 Feb 2021 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.10-0.20201231145340-d24c4e7c9fd0 31 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9 17 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201217193135-6ef4ef7710cc 17 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201217191614-2f4e3cad0f16 17 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201217190214-f84da4cdfa12 17 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201217185503-978b2af59be7 17 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201217184851-b7e51a5ef657 17 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201216195320-d234bb7e4820 16 Dec 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20201129105616-42a16ee1d424 29 Nov 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.9-0.20200819203118-cedfac7102e1 19 Aug 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.8 19 Aug 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.8-0.20200819195910-69c6093c7b23 19 Aug 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224084054-e090a1c4768c 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083955-dc961cc3f7e5 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083941-ecd3419da35a 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083802-2c0b98394eaa 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083743-ef77b79c4ddf 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083727-818631ae61b0 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083553-7dfc1fc2b4ad 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.7-0.20200224083534-f0ae4d07a4ac 24 Feb 2020 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20190220205130-6f934d456d51 20 Feb 2019 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.6 20 Feb 2019 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.6-0.20190220204159-c6e61cc80f62 20 Feb 2019 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.6-0.20190220193807-03ef83617325 20 Feb 2019 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.5 28 Oct 2018 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.5-0.20181028164906-8cf1e3366676 28 Oct 2018 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20180703112113-636d36a76670 03 Jul 2018 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.5-0.20180703112113-636d36a76670 03 Jul 2018 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.5-0.20180624191544-811ab98f8a64 24 Jun 2018 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.5-0.20180624191359-2741d304d3f9 24 Jun 2018 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20170605215311-0c6b41e72360 05 Jun 2017 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.4 05 Jun 2017 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.4-0.20170605213326-d36b8ed83884 05 Jun 2017 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20170215205712-3807218c9f4e 15 Feb 2017 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.4-0.20170215205712-3807218c9f4e 15 Feb 2017 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.3 15 Feb 2017 H2 M1 U2 BSD-3-Clause Yes Details →
v0.0.0-20161202215735-76f94b7c69c6 02 Dec 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.2 02 Dec 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.2-0.20161202213754-4d2db521902f 02 Dec 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.5.1 22 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.4.2-0.20160722223049-d69e41a1a0d5 22 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.4.2-0.20160704160745-198f8c115d12 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.4.2-0.20160704155526-d7a59f1c16a5 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.4.2-0.20160704153640-5378cb15a6eb 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704152841-d2a3602e2500 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704152112-3884c803a1e5 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704151803-657be0cc37b9 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704151440-b94abfad73c1 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704145526-1ee6fb35b4d3 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704143834-2728ddf49813 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704143700-6460df2634c5 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704142705-2b3e9a90a1fc 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704142450-8d7dff6ea532 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704142114-6f9e2d085abc 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704125652-dfe389ef3060 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704125012-e62113f1fb08 04 Jul 2016 H2 M1 U2 BSD-3-Clause Yes Details →
v0.3.2-0.20160704121352-bd6e5ab4220e 04 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160703155048-8da77a461824 03 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160703153809-412a3f9310b3 03 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160703134817-0dd192318137 03 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160703124051-c266d305be98 03 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160703120134-28b5a9f7ff1b 03 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160703114833-84dc759bf908 03 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160702113409-06666ab8aef1 02 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160702111911-79a74470f424 02 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160702104816-f12ea67fc7a7 02 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160702092248-64da4cd6cf5f 02 Jul 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160630123811-23459cc98d76 30 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160630123158-11561616d615 30 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160630120533-4b5b674f4fa7 30 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160630082055-62a04aad7066 30 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160630080851-33c17dc0afac 30 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160628185913-c1f541c34266 28 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160628184757-7e13dbc2f3f4 28 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160628180813-ddf7f92783b8 28 Jun 2016 H2 M1 U2 — Yes Details →
v0.3.2-0.20160422061620-b4769c3d2651 22 Apr 2016 H2 M1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/ulikunitz/xz

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 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/ulikunitz/xz

Is github.com/ulikunitz/xz safe to use?

Vulert records 5 vulnerabilities for github.com/ulikunitz/xz in Go: 0 critical, 2 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/ulikunitz/xz's Vulert package health score?

Vulert scores github.com/ulikunitz/xz 77/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/ulikunitz/xz affected?

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

Which version of github.com/ulikunitz/xz should I use?

v0.5.17 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/ulikunitz/xz have?

5 vulnerabilities are recorded for github.com/ulikunitz/xz in the Go ecosystem: 0 critical, 2 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/ulikunitz/xz vulnerabilities disclosed?

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

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