VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

memoryos: vulnerability history, versions and safety

memoryos is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 39 releases, first recorded in Sep 2026. 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 C1 U1
i
2 with no fix published

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

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

Most recent disclosure 23 Sep 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in PyPI →

See all memoryos vulnerabilities

Vulert verdict on memoryos 2.0.33 i

Updated on 23 Oct 2026

Careful: 2.0.33 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

The current release contains malicious code, which caps this score.

What to do: Do not resolve 2.0.33 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 2.0.33 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 23 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 2 i
  • Malicious packages 1 i
  • Stars 12,032 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, 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 memoryos, 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
2.0.33 03 Sep 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.32 28 Aug 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.30 14 Aug 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.27 31 Jul 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.25 24 Jul 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.24 19 Jul 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.23 09 Jul 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.22 03 Jul 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.20 18 Jun 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.19 12 Jun 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.17 26 May 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.16 19 May 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.15 11 May 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.14 23 Apr 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.13 10 Apr 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.12 07 Apr 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.11 27 Mar 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.10 20 Mar 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.9 16 Mar 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.8 09 Mar 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.7 28 Feb 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.6 12 Feb 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.5 10 Feb 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.4 30 Jan 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.3 23 Jan 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.2 16 Jan 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.1 09 Jan 2026 C1 U1 malicious Apache-2.0 No Details →
2.0.0 24 Dec 2025 C1 U1 malicious Apache-2.0 No Details →
1.1.3 07 Nov 2025 C1 U1 malicious Apache-2.0 No Details →
1.1.2 11 Oct 2025 C1 U1 malicious Apache-2.0 No Details →
1.1.1 24 Sep 2025 C1 U1 malicious Apache-2.0 No Details →
1.0.1 10 Sep 2025 C1 U1 malicious Apache-2.0 No Details →
1.0.0 07 Aug 2025 C1 U1 malicious Apache-2.0 No Details →
0.2.2 29 Jul 2025 C1 U1 malicious Apache-2.0 No Details →
0.2.1 21 Jul 2025 C1 U1 malicious Apache-2.0 No Details →
0.2.0 11 Jul 2025 C1 U1 malicious Apache-2.0 No Details →
0.1.13 09 Jul 2025 C1 U1 malicious Apache-2.0 No Details →
0.1.12 08 Jul 2025 C1 U1 malicious Apache-2.0 No Details →
0.0.1 19 May 2025 C1 U1 malicious Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for memoryos

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious Code Injection in memoryos Package - Critical Vulnerability Detected N/A critical No fix published 23 Sep 2026
Credential Theft Vulnerability in MemoryOS 2.0.34 N/A unrated No fix published 23 Sep 2026

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 memoryos

Is memoryos safe to use?

Vulert records 2 vulnerabilities for memoryos in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is memoryos's Vulert package health score?

Vulert scores memoryos 15/100, which reads as critical. 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 contains malicious code, which caps this score.

Is the latest version of memoryos affected?

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

Which version of memoryos should I use?

2.0.33 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 memoryos have?

2 vulnerabilities are recorded for memoryos in the PyPI ecosystem: 1 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 memoryos vulnerabilities disclosed?

2 vulnerabilities were recorded for memoryos in the last 12 months, and the oldest entry in this database dates to 23 Sep 2026. 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 memoryos 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor memoryos for upcoming vulnerabilities?

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