Vulnerability Database · Go · Package report

github.com/vbatts/tar-split: vulnerability history, versions and safety

github.com/vbatts/tar-split is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 114 releases, from May 2022 to Apr 2025. 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.

Vulert verdict on github.com/vbatts/tar-split v0.12.3 i

Updated on 23 Oct 2026

Action needed: v0.12.3 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 69/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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.12.3 — affected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 24 Apr 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 112 i
  • OpenSSF scorecard 2/10 i
  • Last release 5 months ago i
  • Licence BSD-3-Clause 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/vbatts/tar-split, 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.12.4-0.20260930154653-defbac34c659 30 Sep 2026 M1 U1 BSD-3-Clause Yes Details →
v0.12.3 27 Apr 2026 M1 U1 BSD-3-Clause Yes Details →
v0.12.3-0.20260318133050-e4eab4e5b85a 18 Mar 2026 M1 U1 BSD-3-Clause Yes Details →
v0.12.2 14 Oct 2025 M1 U1 BSD-3-Clause Yes Details →
v0.12.1 30 Jan 2025 M1 U1 BSD-3-Clause Yes Details →
v0.12.0 29 Jan 2025 M1 U1 BSD-3-Clause Yes Details →
v0.11.8-0.20250128160447-c8b16f6803a3 28 Jan 2025 M1 U1 BSD-3-Clause Yes Details →
v0.11.7 20 Jan 2025 M1 U1 BSD-3-Clause Yes Details →
v0.11.7-0.20241024173430-cc780eeb0b3f 24 Oct 2024 M1 U1 BSD-3-Clause Yes Details →
v0.11.7-0.20241021145534-b29a6c061360 21 Oct 2024 M1 U1 BSD-3-Clause Yes Details →
v0.11.7-0.20241021143358-18eabcdcca79 21 Oct 2024 M1 U1 BSD-3-Clause Yes Details →
v0.11.6 27 Sep 2024 M1 U1 BSD-3-Clause Yes Details →
v0.11.6-0.20240927001420-1f44cc4dc323 27 Sep 2024 M1 U1 BSD-3-Clause Yes Details →
v0.11.6-0.20240911180149-99c8914877e1 11 Sep 2024 M1 U1 BSD-3-Clause Yes Details →
v0.11.6-0.20230826122636-fe4605ae8b2a 26 Aug 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.6-0.20230826082345-bd00927367c4 26 Aug 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.5 22 Jul 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.5-0.20230722170938-5ef0dd824316 22 Jul 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4 21 Jul 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4-0.20230721131047-9982e470fa34 21 Jul 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4-0.20230720154106-db25994f5bcf 20 Jul 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4-0.20230427181940-f966b140968a 27 Apr 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4-0.20230427181207-724d595c0385 27 Apr 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4-0.20230326182038-58175ba39623 26 Mar 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.4-0.20230326025336-16d1376be976 26 Mar 2023 M1 U1 BSD-3-Clause Yes Details →
v0.11.3 26 Mar 2023 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20210823101835-80a436fd6164 23 Aug 2021 M1 U1 BSD-3-Clause Yes Details →
v0.11.2 23 Aug 2021 M1 U1 BSD-3-Clause Yes Details →
v0.11.2-0.20210821012439-8d7636308555 21 Aug 2021 M1 U1 BSD-3-Clause Yes Details →
v0.11.2-0.20201028113245-05e7c395fb2c 28 Oct 2020 M1 U1 BSD-3-Clause Yes Details →
v0.11.2-0.20201028001930-4b50e3822d49 28 Oct 2020 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20181022144918-620714a4c508 22 Oct 2018 M1 U1 BSD-3-Clause Yes Details →
v0.10.3-0.20181022144918-620714a4c508 22 Oct 2018 M1 U1 BSD-3-Clause Yes Details →
v0.11.1 22 Oct 2018 M1 U1 BSD-3-Clause Yes Details →
v0.11.1-0.20181017235754-dbab9ab4fb86 17 Oct 2018 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20180906123440-61b49a82bb34 06 Sep 2018 M1 U1 BSD-3-Clause Yes Details →
v0.11.0 06 Sep 2018 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20180223144638-e48992827207 23 Feb 2018 M1 U1 BSD-3-Clause Yes Details →
v0.10.3-0.20180223144638-e48992827207 23 Feb 2018 M1 U1 BSD-3-Clause Yes Details →
v0.10.3-0.20180223134206-a9de541771e5 23 Feb 2018 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20171107153949-38ec4ddb06de 07 Nov 2017 M1 U1 BSD-3-Clause Yes Details →
v0.10.2 07 Nov 2017 M1 U1 BSD-3-Clause Yes Details →
v0.10.2-0.20170901084509-22999e8f9656 01 Sep 2017 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20170314152438-b9127a139315 14 Mar 2017 M1 U1 BSD-3-Clause Yes Details →
v0.10.2-0.20170314152438-b9127a139315 14 Mar 2017 M1 U1 BSD-3-Clause Yes Details →
v0.10.2-0.20170314123813-245403c324d6 14 Mar 2017 M1 U1 BSD-3-Clause Yes Details →
v0.3.1 20 Jan 2017 M1 U1 BSD-3-Clause Yes Details →
v0.3.0 08 Dec 2016 M1 U1 BSD-3-Clause Yes Details →
v0.2.1-0.20161111170149-690c85d4e826 11 Nov 2016 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20160927025418-bd4c5d64c3e9 27 Sep 2016 M1 U1 BSD-3-Clause Yes Details →
v0.10.2-0.20160927025418-bd4c5d64c3e9 27 Sep 2016 M1 U1 BSD-3-Clause Yes Details →
v0.10.1 26 Sep 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.14-0.20160926223147-416fa5dcfe18 26 Sep 2016 M1 U1 BSD-3-Clause Yes Details →
v0.10.0 23 Sep 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.14-0.20160923003818-e527e70d2599 23 Sep 2016 M1 U1 BSD-3-Clause Yes Details →
v0.2.0 16 Aug 2016 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20160726135008-6810cedb21b2 26 Jul 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.14-0.20160726135008-6810cedb21b2 26 Jul 2016 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20160626190037-28bc4c32f9fa 26 Jun 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.14-0.20160626190037-28bc4c32f9fa 26 Jun 2016 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20160330203851-226f7c74905f 30 Mar 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.14-0.20160330203851-226f7c74905f 30 Mar 2016 M1 U1 BSD-3-Clause Yes Details →
v0.0.0-20160229164038-e2a62d6b0d98 29 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.14-0.20160229164038-e2a62d6b0d98 29 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13 15 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13-0.20160203120109-10db8408f660 03 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13-0.20160202193227-64935a5f0f25 02 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13-0.20160202191011-2424f4e36723 02 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13-0.20160202190838-cb423795ebbe 02 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13-0.20160202190630-440ba9e519d0 02 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.13-0.20160202190630-4ad443d1668a 02 Feb 2016 M1 U1 BSD-3-Clause Yes Details →
v0.9.12 03 Dec 2015 M1 U1 BSD-3-Clause Yes Details →
v0.9.11 02 Dec 2015 M1 U1 MIT Yes Details →
v0.9.11-0.20151202180026-026e78012bc3 02 Dec 2015 M1 U1 MIT Yes Details →
v0.0.0-20151201220853-23b6435e6bb9 01 Dec 2015 M1 U1 MIT Yes Details →
v0.9.11-0.20151201220853-23b6435e6bb9 01 Dec 2015 M1 U1 MIT Yes Details →
v0.9.11-0.20151201203710-93666d582404 01 Dec 2015 M1 U1 MIT Yes Details →
v0.9.11-0.20151201203148-11281e8c0930 01 Dec 2015 M1 U1 MIT Yes Details →
v0.9.11-0.20151016204109-7ea74e1c31d4 16 Oct 2015 M1 U1 MIT Yes Details →
v0.9.10 25 Sep 2015 M1 U1 MIT Yes Details →
v0.9.10-0.20150925183512-10250c25e0cb 25 Sep 2015 M1 U1 MIT Yes Details →
v0.9.9 24 Sep 2015 M1 U1 MIT Yes Details →
v0.9.8 23 Sep 2015 M1 U1 MIT Yes Details →
v0.9.8-0.20150923192733-032efafc2963 23 Sep 2015 M1 U1 MIT Yes Details →
v0.9.8-0.20150903190125-414a687f8343 03 Sep 2015 M1 U1 MIT Yes Details →
v0.9.8-0.20150821042541-b4d27b54261d 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-27e18409b9d3 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-2e5698249c89 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-3b34dbd368ec 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-55dceefe42a7 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-576b2737620b 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-69de764807da 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-6e38573de2ab 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150821041522-b48c28014e68 21 Aug 2015 M1 U1 MIT Yes Details →
v0.9.7-0.20150818185432-bf82db1f0de5 18 Aug 2015 M1 U1 MIT Yes Details →
v0.9.6 13 Aug 2015 M1 U1 MIT Yes Details →
v0.9.5 11 Aug 2015 M1 U1 MIT Yes Details →
v0.9.5-0.20150728194524-de37d1755a80 28 Jul 2015 M1 U1 MIT Yes Details →
v0.9.4 22 Jul 2015 M1 U1 MIT Yes Details →
v0.9.3 21 Jul 2015 M1 U1 — Yes Details →
v0.9.3-0.20150720204622-04172717dedf 20 Jul 2015 M1 U1 — Yes Details →
v0.9.2 15 Jul 2015 M1 U1 — Yes Details →
v0.9.1 23 Jun 2015 M1 U1 — Yes Details →
v0.9.1-0.20150621181532-174287a8aa37 21 Jun 2015 M1 U1 — Yes Details →
v0.9.0 10 Mar 2015 M1 U1 — Yes Details →
v0.0.0-20150309181940-032423140a2c 09 Mar 2015 M1 U1 — Yes Details →
v0.0.0-20150303192304-4f1bde4d1378 03 Mar 2015 M1 U1 — Yes Details →
v0.0.0-20150228174755-ccf6fa61a69c 28 Feb 2015 M1 U1 — Yes Details →
v0.0.0-20150225194049-081c5b9feb8b 25 Feb 2015 M1 U1 — Yes Details →
v0.0.0-20150220204621-42fb83004d7c 20 Feb 2015 M1 U1 — Yes Details →
v0.0.0-20150219230722-739daf3e09bd 19 Feb 2015 M1 U1 — Yes Details →
v0.0.0-20150211132407-2ab5fedc6c3d 11 Feb 2015 M1 U1 — Yes Details →
v0.0.0-20150203222941-70b9150cff0f 03 Feb 2015 M1 U1 — Yes Details →

All 114 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2025 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 github.com/vbatts/tar-split

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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/vbatts/tar-split

Is github.com/vbatts/tar-split safe to use?

Vulert records 2 vulnerabilities for github.com/vbatts/tar-split 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 github.com/vbatts/tar-split's Vulert package health score?

Vulert scores github.com/vbatts/tar-split 69/100, which reads as usable, but worth attention. 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/vbatts/tar-split affected?

Yes. v0.12.3, 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/vbatts/tar-split should I use?

v0.12.3 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/vbatts/tar-split have?

2 vulnerabilities are recorded for github.com/vbatts/tar-split 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 github.com/vbatts/tar-split vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/vbatts/tar-split in the last 12 months, and the oldest entry in this database dates to 17 May 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/vbatts/tar-split 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/vbatts/tar-split for upcoming vulnerabilities?

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