VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

modernc.org/memory: vulnerability history, versions and safety

modernc.org/memory is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

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 modernc.org/memory vulnerabilities

Vulert verdict on modernc.org/memory v1.12.1 i

Updated on 23 Oct 2026

Good news: v1.12.1, the version you would install today, has no known vulnerabilities.

Package health score 74/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v1.12.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.12.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.12.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 6 i
  • Last release 2 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 modernc.org/memory, 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.12.1 19 Aug 2026 none BSD-3-Clause — Details →
v1.12.1-0.20260819163649-bb3d99379ed7 19 Aug 2026 none BSD-3-Clause — Details →
v1.12.0 06 Aug 2026 none BSD-3-Clause — Details →
v1.11.0 17 May 2025 none BSD-3-Clause — Details →
v1.10.0 15 Apr 2025 none BSD-3-Clause — Details →
v0.0.0-20250413151623-5379045fd6ab 13 Apr 2025 none BSD-3-Clause — Details →
v1.9.1 20 Mar 2025 none BSD-3-Clause — Details →
v1.9.0 17 Mar 2025 none BSD-3-Clause — Details →
v1.8.2 13 Jan 2025 none BSD-3-Clause — Details →
v1.8.1 27 Dec 2024 none BSD-3-Clause — Details →
v1.7.3-0.20240403163548-cd6b9df5067a 03 Apr 2024 none BSD-3-Clause — Details →
v1.8.0 03 Apr 2024 none BSD-3-Clause — Details →
v1.7.3-0.20240403160940-16ce6fcaf7af 03 Apr 2024 none BSD-3-Clause — Details →
v1.7.3-0.20240403160940-44d59e58017c 03 Apr 2024 none BSD-3-Clause — Details →
v1.7.2 25 Sep 2023 none BSD-3-Clause — Details →
v1.7.2-0.20230925140719-dda74182ee99 25 Sep 2023 none BSD-3-Clause — Details →
v1.7.2-0.20230925134911-f52125d2ec51 25 Sep 2023 none BSD-3-Clause — Details →
v1.7.1 23 Aug 2023 none BSD-3-Clause — Details →
v1.6.1-0.20230628082219-fc5eddbb190c 28 Jun 2023 none BSD-3-Clause — Details →
v1.7.0 28 Jun 2023 none BSD-3-Clause — Details →
v1.6.0 19 May 2023 none BSD-3-Clause — Details →
v1.5.0 04 Dec 2022 none BSD-3-Clause — Details →
v1.4.1-0.20221204103301-81613c9e018a 04 Dec 2022 none BSD-3-Clause — Details →
v1.4.1-0.20221204103215-edbd0c0f5080 04 Dec 2022 none BSD-3-Clause — Details →
v1.4.1-0.20221204102432-91a833d1160b 04 Dec 2022 none BSD-3-Clause — Details →
v1.4.0 14 Sep 2022 none BSD-3-Clause — Details →
v1.3.1-0.20220904194221-2fd15faf5f35 04 Sep 2022 none BSD-3-Clause — Details →
v0.0.0-20220904151635-f8b5f11b2afe 04 Sep 2022 none BSD-3-Clause — Details →
v1.2.2-0.20220904151635-f8b5f11b2afe 04 Sep 2022 none BSD-3-Clause — Details →
v1.3.0 04 Sep 2022 none BSD-3-Clause — Details →
v1.2.1 25 Aug 2022 none BSD-3-Clause — Details →
v1.2.1-0.20220825141257-4303fbc5fb9f 25 Aug 2022 none BSD-3-Clause — Details →
v1.2.0 30 Jul 2022 none BSD-3-Clause — Details →
v1.1.1 28 Apr 2022 none BSD-3-Clause — Details →
v1.1.0 14 Apr 2022 none BSD-3-Clause — Details →
v1.0.8-0.20220414095726-cd842ab20af8 14 Apr 2022 none BSD-3-Clause — Details →
v1.0.7 21 Mar 2022 none BSD-3-Clause — Details →
v1.0.7-0.20220321122741-7ff42bc936ce 21 Mar 2022 none BSD-3-Clause — Details →
v1.0.7-0.20220321122741-85f19eb0aae4 21 Mar 2022 none BSD-3-Clause — Details →
v1.0.6 07 Mar 2022 none BSD-3-Clause — Details →
v1.0.6-0.20220306044613-78cfad939eb2 06 Mar 2022 none BSD-3-Clause — Details →
v1.0.6-0.20220124130336-ad8c8bd4ca32 24 Jan 2022 none BSD-3-Clause — Details →
v1.0.6-0.20220124111123-2f522b72d48d 24 Jan 2022 none BSD-3-Clause — Details →
v1.0.5 03 Jul 2021 none BSD-3-Clause — Details →
v1.0.4 23 Nov 2020 none BSD-3-Clause — Details →
v1.0.3 23 Nov 2020 none BSD-3-Clause — Details →
v1.0.2 20 Nov 2020 none BSD-3-Clause — Details →
v1.0.1 07 Sep 2020 none BSD-3-Clause — Details →
v1.0.1-0.20181208123210-0b21df26c47f 08 Dec 2018 none BSD-3-Clause — Details →
v1.0.0 06 Nov 2018 none BSD-3-Clause — Details →
v0.0.0-20170609194654-34cb9988dc0d 09 Jun 2017 none BSD-3-Clause — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for modernc.org/memory

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 modernc.org/memory

Is modernc.org/memory safe to use?

Vulert has no vulnerabilities on record for modernc.org/memory in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is modernc.org/memory's Vulert package health score?

Vulert scores modernc.org/memory 74/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 modernc.org/memory affected?

No. v1.12.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of modernc.org/memory should I use?

v1.12.1 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 modernc.org/memory have?

0 vulnerabilities are recorded for modernc.org/memory in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new modernc.org/memory vulnerabilities disclosed?

0 vulnerabilities were recorded for modernc.org/memory in the last 12 months. 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 modernc.org/memory 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 modernc.org/memory for upcoming vulnerabilities?

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