VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ipfs/go-unixfsnode: vulnerability history, versions and safety

github.com/ipfs/go-unixfsnode is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 94 releases, first recorded in Feb 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 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.

See all github.com/ipfs/go-unixfsnode vulnerabilities

Vulert verdict on github.com/ipfs/go-unixfsnode v1.10.6 i

Updated on 23 Oct 2026

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

Package health score 64/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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.10.6 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 14 Feb 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 15 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 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/ipfs/go-unixfsnode, 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.10.6 27 Jul 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.6-0.20260726230606-70b7b4e8854e 26 Jul 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.5 09 Jul 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.5-0.20260709012559-da47d415e73c 09 Jul 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.5-0.20260707180847-601255a32f51 07 Jul 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.4 27 Apr 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.3 16 Feb 2026 H1 U2 Apache-2.0 Yes Details →
v1.10.2 18 Sep 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.2-0.20250821051736-c73e6ac3d32c 21 Aug 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.2-0.20250821050343-2cce047ed69c 21 Aug 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.2-0.20250821045454-b742ca720104 21 Aug 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.1 28 May 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.1-0.20250527235451-22f37878c292 27 May 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.1-0.20250328130823-6c8f8e1cfab4 28 Mar 2025 H1 U2 Apache-2.0 Yes Details →
v1.10.0 18 Feb 2025 H1 U2 Apache-2.0 Yes Details →
v1.9.3-0.20250216200236-a91c356ad5c9 16 Feb 2025 H1 U2 Apache-2.0 Yes Details →
v1.9.2 21 Oct 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.2-0.20241021170131-1c19c59f1ab9 21 Oct 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.2-0.20241021005242-ccf22c4e5a15 21 Oct 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.2-0.20241018192014-35715966159a 18 Oct 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1 26 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240826151056-8151e6f66ca1 26 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240826091749-b3612b6b021f 26 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240826091539-c255989e68c4 26 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240826010600-fbaaad7c228b 26 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240322071822-c41f115d06cf 22 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240314112651-8b88b91fe9a4 14 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.9.1-0.20240131173448-3b05dbdec817 31 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.8.2-0.20230927010056-24673576b134 27 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.9.0 27 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.8.2-0.20230926094609-262973f68de6 26 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.8.2-0.20230925043011-4ff13ddbce13 25 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.8.1 19 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.8.1-0.20230919093634-f06958fcd374 19 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.8.1-0.20230918113936-6f1f7afd4250 18 Sep 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.5-0.20230826000414-62611f5c9d70 26 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.8.0 26 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.5-0.20230814133659-7db26c0c9ffb 14 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.5-0.20230814020426-223e4e1272f8 14 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.5-0.20230813165636-edfeeb835a4d 13 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.4 10 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.4-0.20230810102853-dd4daeefc8dd 10 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.3 25 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.3-0.20230725065206-a1cbf13f5c5f 25 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.3-0.20230721080340-393a5383fa4a 21 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.3-0.20230721080204-a731afe59509 21 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.3-0.20230718163022-62f4a1c8d46e 18 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.3-0.20230718162021-3cad2f7e6def 18 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2 07 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2-0.20230707143404-09dd8c85fd84 07 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2-0.20230707142712-056398d7a09f 07 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2-0.20230707090412-166be19558d9 07 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2-0.20230628085008-364a5496925b 28 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2-0.20230622024455-de5cbf74cbe0 22 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.2-0.20230614111248-89eedd7b3438 14 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.1 02 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.1-0.20230602141211-1f8efbad2b0d 02 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.7.0 17 May 2023 H1 U2 Apache-2.0 Yes Details →
v1.6.1-0.20230517053421-699a259c50e7 17 May 2023 H1 U2 Apache-2.0 Yes Details →
v1.6.1-0.20230512023323-57f993f68bd3 12 May 2023 H1 U2 Apache-2.0 Yes Details →
v1.6.0 13 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.3-0.20230309062929-51109f599b35 09 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.3-0.20230309032732-ca00f89a2119 09 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.3-0.20230308034728-3958404b70c0 08 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.3-0.20230308024752-a1d05669bb7a 08 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.2 09 Feb 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.2-0.20230209192830-a4ed723727e0 09 Feb 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.2-0.20230126175703-91b3d39d33ef 26 Jan 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.1 09 Jan 2023 H1 U2 Apache-2.0 Yes Details →
v1.5.1-0.20221015154338-475ed658c35e 15 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.5.0 25 Aug 2022 H1 U2 Apache-2.0 Yes Details →
v1.4.1-0.20220503015421-31cb5601868f 03 May 2022 H1 U2 Apache-2.0 Yes Details →
v1.4.1-0.20220502093700-f664db4b2168 02 May 2022 H1 U2 Apache-2.0 Yes Details →
v1.4.1-0.20220404162956-62f7ce28de6b 04 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.4.0 09 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.3.0 07 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20220307162924-9214f706a1fb 07 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20220303111128-94986a76305a 03 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.2.0 13 Jan 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220110213426-c487b3de0a4e 10 Jan 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220110204839-1b00a5a75ce5 10 Jan 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20211221201818-b2ae22e83798 21 Dec 2021 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20211210154015-7397bdd74ab0 10 Dec 2021 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20211105121048-b9b6e9dc571e 05 Nov 2021 H1 U2 — Yes Details →
v1.1.4-0.20211029111512-28f6929528fc 29 Oct 2021 H1 U2 — Yes Details →
v1.1.4-0.20211018205408-e0bbe4aca062 18 Oct 2021 H1 U2 — Yes Details →
v1.1.3 27 Sep 2021 H1 U2 — Yes Details →
v1.1.2 12 Aug 2021 H1 U2 — Yes Details →
v1.1.1 05 Apr 2021 H1 U2 — Yes Details →
v1.1.0 04 Apr 2021 H1 U2 — Yes Details →
v1.0.1-0.20210402214142-de45652f269f 02 Apr 2021 H1 U2 — Yes Details →
v1.0.0 17 Mar 2021 H1 U2 — Yes Details →
v0.0.0-20210308221042-a4d497dc9639 08 Mar 2021 H1 U2 — Yes Details →
v0.0.0-20210305044005-f2af51ae85c1 05 Mar 2021 H1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/ipfs/go-unixfsnode

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-23631: IPFS go-unixfsnode DOS via HAMT Decoding Panics 7.5 high 1.5.2 10 Feb 2023
CVE-2023-23631: IPFS go-unixfsnode DOS via HAMT Decoding Panics N/A unrated 1.5.2 14 Feb 2023
CVE-2023-23631: Denial of Service in github.com/ipfs/go-unixfsnode N/A unrated 1.5.2 14 Feb 2023

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/ipfs/go-unixfsnode

Is github.com/ipfs/go-unixfsnode safe to use?

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

Vulert scores github.com/ipfs/go-unixfsnode 64/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/ipfs/go-unixfsnode affected?

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

Which version of github.com/ipfs/go-unixfsnode should I use?

v1.10.6 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/ipfs/go-unixfsnode have?

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

0 vulnerabilities were recorded for github.com/ipfs/go-unixfsnode in the last 12 months, and the oldest entry in this database dates to 10 Feb 2023. 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/ipfs/go-unixfsnode 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/ipfs/go-unixfsnode for upcoming vulnerabilities?

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