Vulnerability Database · Go · Package report

github.com/sassoftware/go-rpmutils: vulnerability history, versions and safety

github.com/sassoftware/go-rpmutils is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 85 releases, from Apr 2021 to Jun 2021. 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 H1 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/sassoftware/go-rpmutils v0.4.0 i

Updated on 23 Oct 2026

Action needed: v0.4.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 63/100
  • Security Minor issues
  • Maintenance Maintaining
  • 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.4.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 23 Jun 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 58 i
  • OpenSSF scorecard 4/10 i
  • Last release 29 months ago 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 github.com/sassoftware/go-rpmutils, 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.0.0-20260617125058-3287a81e7bd7 17 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v0.4.1-0.20260617125058-3287a81e7bd7 17 Jun 2026 H1 U1 Apache-2.0 Yes Details →
v0.4.1-0.20250318174028-2660c86d578c 18 Mar 2025 H1 U1 Apache-2.0 Yes Details →
v0.3.1-0.20240507153815-9cc5954158fe 07 May 2024 H1 U1 Apache-2.0 Yes Details →
v0.4.0 07 May 2024 H1 U1 Apache-2.0 Yes Details →
v0.3.1-0.20240417214154-48bac67d7895 17 Apr 2024 H1 U1 Apache-2.0 Yes Details →
v0.3.1-0.20240417150844-6356a5a73e20 17 Apr 2024 H1 U1 Apache-2.0 Yes Details →
v0.3.1-0.20240126183508-fdadba30667f 26 Jan 2024 H1 U1 Apache-2.0 Yes Details →
v0.3.1-0.20240126182337-80e9756b0da4 26 Jan 2024 H1 U1 Apache-2.0 Yes Details →
v0.2.1-0.20240126160712-d2036ff8d896 26 Jan 2024 H1 U1 Apache-2.0 Yes Details →
v0.3.0 26 Jan 2024 H1 U1 Apache-2.0 Yes Details →
v0.2.1-0.20240124161140-277b154961dd 24 Jan 2024 H1 U1 Apache-2.0 Yes Details →
v0.2.1-0.20230922000323-01eb0ea01fc3 22 Sep 2023 H1 U1 Apache-2.0 Yes Details →
v0.2.1-0.20220419081909-d2202c0fc005 19 Apr 2022 H1 U1 Apache-2.0 Yes Details →
v0.1.2-0.20210408161218-1a98ab0ca3f2 08 Apr 2021 H1 U1 Apache-2.0 Yes Details →
v0.2.0 08 Apr 2021 H1 U1 Apache-2.0 Yes Details →
v0.1.2-0.20210127001923-e5cf0f808585 27 Jan 2021 H1 U1 Apache-2.0 Yes Details →
v0.1.2-0.20210125232425-bca3825719db 25 Jan 2021 H1 U1 Apache-2.0 Yes Details →
v0.1.2-0.20210125231624-af36da7a6923 25 Jan 2021 H1 U1 Apache-2.0 Yes Details →
v0.1.2-0.20200801133646-372bd0b0a03f 01 Aug 2020 H1 U1 Apache-2.0 Yes Details →
v0.1.1 12 Jun 2020 H1 U1 Apache-2.0 Yes Details →
v0.1.0 12 Jun 2020 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20200612152245-a64058cf21b8 12 Jun 2020 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20200612150239-e314ffa6ce54 12 Jun 2020 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20190420191620-a8f1baeba37b 20 Apr 2019 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20190411140044-ff0a6f56745c 11 Apr 2019 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20190125002135-4cb60bc02315 25 Jan 2019 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20180124145353-8c470ded63c3 24 Jan 2018 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20180108103223-a9675eebf375 08 Jan 2018 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20180108103031-c08a07527b87 08 Jan 2018 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20180103150414-6535cfb30cfa 03 Jan 2018 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20171230134541-ed6e71e402dc 30 Dec 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170920195927-1eab34795a29 20 Sep 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170907163507-d723427f8b18 07 Sep 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170720220739-d9054a3bb17e 20 Jul 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170720153209-3883a120f81a 20 Jul 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170720144754-8af0d9112b4a 20 Jul 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170720143201-7db7b8ebaa12 20 Jul 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170720143136-d27c6bc38493 20 Jul 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170330204246-c2369def574f 30 Mar 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170329033454-960e515f7232 29 Mar 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170320005611-23f1c608097c 20 Mar 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170320005554-0f697b394b7c 20 Mar 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170308144807-9655c9336de7 08 Mar 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170308144517-fe5f33dad99e 08 Mar 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170206152125-5ed137950c4a 06 Feb 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170203191640-95f7d12b6fa9 03 Feb 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170122165503-7047eb1a673f 22 Jan 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170109190954-c8d604861e80 09 Jan 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20170104182947-afcdef956248 04 Jan 2017 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20161129231829-fac6074dc1f4 29 Nov 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20161129230237-b5e9b314f506 29 Nov 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160920144644-341ec856c680 20 Sep 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160920143259-ab1278c12dab 20 Sep 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160606235717-173536802104 06 Jun 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160601014849-dde40e7d8be7 01 Jun 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160531224114-0ca7828a87ff 31 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160531212803-1a5cf75c0e11 31 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160527174852-b8ffd896bbb3 27 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160526190743-022b5e80a885 26 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160526150635-2ffccfb4a644 26 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160525184807-24e49cfd5d3a 25 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160525184757-2580f35317a8 25 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160525184610-636d81b188bc 25 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160525184425-c8f98479d1e2 25 May 2016 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20160525184345-7ea5ac6028d5 25 May 2016 H1 U1 — Yes Details →
v0.0.0-20160525011105-8629cf186e91 25 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524012416-2d4335a5707e 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524012123-e2cb82455d7b 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524011605-e555336868f5 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524011053-1528437e7921 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524010933-89ad7bb93945 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524001346-52c63b1de6ba 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524001255-7a95ab0ec773 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160524001053-408eddd9c687 24 May 2016 H1 U1 — Yes Details →
v0.0.0-20160523215453-b6871cdc60ee 23 May 2016 H1 U1 — Yes Details →
v0.0.0-20160521030647-0dcce9f73c4c 21 May 2016 H1 U1 — Yes Details →
v0.0.0-20160521030531-37b38df18747 21 May 2016 H1 U1 — Yes Details →
v0.0.0-20160520204142-9063433817f0 20 May 2016 H1 U1 — Yes Details →
v0.0.0-20160513011849-bcb1c8dd1468 13 May 2016 H1 U1 — Yes Details →
v0.0.0-20160512185659-a146fc96e12a 12 May 2016 H1 U1 — Yes Details →
v0.0.0-20160512173029-ef816aa2263f 12 May 2016 H1 U1 — Yes Details →
v0.0.0-20160504014101-bbe7dd9c3dbd 04 May 2016 H1 U1 — Yes Details →
v0.0.0-20160503221433-28ad8b13023c 03 May 2016 H1 U1 — Yes Details →
v0.0.0-20140808164158-ce8a089be783 08 Aug 2014 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

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/sassoftware/go-rpmutils

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/sassoftware/go-rpmutils

Is github.com/sassoftware/go-rpmutils safe to use?

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

Vulert scores github.com/sassoftware/go-rpmutils 63/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/sassoftware/go-rpmutils affected?

Yes. v0.4.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/sassoftware/go-rpmutils should I use?

v0.4.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/sassoftware/go-rpmutils have?

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

0 vulnerabilities were recorded for github.com/sassoftware/go-rpmutils 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/sassoftware/go-rpmutils 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/sassoftware/go-rpmutils for upcoming vulnerabilities?

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