VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/nwaples/rardecode: vulnerability history, versions and safety

github.com/nwaples/rardecode is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 75 releases, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 05 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/nwaples/rardecode vulnerabilities

Vulert verdict on github.com/nwaples/rardecode v1.1.3 i

Updated on 23 Oct 2026

Careful: v1.1.3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 53/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v1.1.3 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 05 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 147 i
  • OpenSSF scorecard 2/10 i
  • Last release 55 months ago i
  • Licence BSD-2-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/nwaples/rardecode, 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.1.3 06 Mar 2022 U1 BSD-2-Clause No Details →
v1.1.3-0.20220306032531-434b4a38896d 06 Mar 2022 U1 BSD-2-Clause No Details →
v1.1.2 08 Aug 2021 U1 BSD-2-Clause No Details →
v1.1.1 17 Jul 2021 U1 BSD-2-Clause No Details →
v1.1.1-0.20210717080254-d72e53bd9f6b 17 Jul 2021 U1 BSD-2-Clause No Details →
v0.0.0-20210717073713-4a86a5b1928c 17 Jul 2021 U1 BSD-2-Clause No Details →
v2.0.0-20210717073713-4a86a5b1928c+incompatible 17 Jul 2021 U1 BSD-2-Clause No Details →
v0.0.0-20200222004035-ebfbc92756ab 22 Feb 2020 U1 BSD-2-Clause No Details →
v1.1.0 21 Feb 2020 U1 BSD-2-Clause No Details →
v0.0.0-20181025094117-197ef08ef68c 25 Oct 2018 U1 BSD-2-Clause No Details →
v1.0.1-0.20181025094117-197ef08ef68c 25 Oct 2018 U1 BSD-2-Clause No Details →
v1.0.0 21 Oct 2018 U1 BSD-2-Clause No Details →
v0.0.0-20171119074530-07c6e2c16e29 19 Nov 2017 U1 BSD-2-Clause No Details →
v0.0.0-20171118064515-c50dc909f153 18 Nov 2017 U1 BSD-2-Clause No Details →
v0.0.0-20171117101057-d6e759c9dcb8 17 Nov 2017 U1 BSD-2-Clause No Details →
v0.0.0-20171029023500-e06696f847ae 29 Oct 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170924055942-a1b8c73387aa 24 Sep 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170805073545-751b9fbd3ff1 05 Aug 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170805062553-1509af263ff3 05 Aug 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170318050745-9027bb4f2ca4 18 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170316222737-53f24e78d0b0 16 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170315005450-3ca810192db8 15 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170313211748-2e103b6385f6 13 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170313093648-04c3f9b3696f 13 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170311223025-1e01fdd5fa75 11 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170309230230-1d71f047795f 09 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170303061511-22e14c90fd6b 03 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170301075616-53ca318777fc 01 Mar 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170226103641-92e7caabe629 26 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170225003826-092c12e0f45f 25 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170224103528-ce8901e3bfdf 24 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170223081712-3e1ce6785582 23 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170222013021-2de46bc6e11d 22 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170220234134-058868fc2ae1 20 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170220042533-028ce317cdc8 20 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170218062324-47774fd00319 18 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170217002717-33b8e21301f5 17 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170216024338-58f09860f42d 16 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170215020030-2af2b7269d89 15 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170209070120-bda08ccbf9a5 09 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170208010935-8d1f31779c09 08 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170207014926-5b5c277a10c5 07 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170206011250-19fb1484c02d 06 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170205074323-117811675de8 05 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170204063244-4238d3721aad 04 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170203035506-ace1fbea5717 03 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170202034331-09acc18378e8 02 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170201064257-78a4df25443c 01 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170201001016-1d0cb94fac2b 01 Feb 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170131023325-1ef5f435dd83 31 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170130085923-bac0c9edb046 30 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170129044954-b2263c93570d 29 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170127062019-0d3473b799c9 27 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170126094025-a9a87f94998f 26 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170112110516-f22b7ef81a0a 12 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170109140719-0e1fd1377581 09 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170109121046-471af34fa709 09 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170107104502-29541495f523 07 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20170106054431-2534663f8930 06 Jan 2017 U1 BSD-2-Clause No Details →
v0.0.0-20161222234428-18e2160743d3 22 Dec 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160723083021-f94841372ddc 23 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160723033738-89cfd411044f 23 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160713080656-7b958952f24d 13 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160713075912-00fa1efe8c6a 13 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160707093232-a59299d0638a 07 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160706064047-3a61be3dbde6 06 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160706010516-ac62f7c23979 06 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160705085205-2df533f1530a 05 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160704025836-2b6967612a14 04 Jul 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160123072043-7efb1e632fbe 23 Jan 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160123071732-302f98bd5297 23 Jan 2016 U1 BSD-2-Clause No Details →
v0.0.0-20160122165033-f091811c6b77 22 Jan 2016 U1 BSD-2-Clause No Details →
v0.0.0-20150714002714-88c23d3db3ab 14 Jul 2015 U1 BSD-2-Clause No Details →
v0.0.0-20150610033316-2eb4348e3e2f 10 Jun 2015 U1 — No Details →
v0.0.0-20150323094838-210a08323fa5 23 Mar 2015 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/nwaples/rardecode

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-11579: DoS Risk in github.com/nwaples/rardecode Due to Unrestricted RAR Dictionary Sizes N/A unrated No fix published 05 Nov 2025

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/nwaples/rardecode

Is github.com/nwaples/rardecode safe to use?

Vulert records 1 vulnerabilities for github.com/nwaples/rardecode in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/nwaples/rardecode's Vulert package health score?

Vulert scores github.com/nwaples/rardecode 53/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/nwaples/rardecode affected?

Yes. v1.1.3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/nwaples/rardecode should I use?

v1.1.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/nwaples/rardecode have?

1 vulnerability is recorded for github.com/nwaples/rardecode in the Go ecosystem: 0 critical, 0 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/nwaples/rardecode vulnerabilities disclosed?

1 vulnerability was recorded for github.com/nwaples/rardecode in the last 12 months, and the oldest entry in this database dates to 05 Nov 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/nwaples/rardecode 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/nwaples/rardecode for upcoming vulnerabilities?

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