VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

admesh: vulnerability history, versions and safety

admesh is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 14 releases, from May 2022 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 18 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all admesh vulnerabilities

Vulert verdict on admesh 0.98.9 i

Updated on 23 Oct 2026

Action needed: 0.98.9 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 45/100
  • Security Some issues to review
  • Maintenance Slowing
  • 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 0.98.9 — affected i
  • Vulnerabilities on record 5 over 3 years · 1 in the last year i
  • Latest disclosure 18 Feb 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 9 i
  • OpenSSF scorecard 1/10 i
  • Last release 99 months ago i
  • Licence non-standard 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 admesh, 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
0.98.9 24 Jun 2018 U1 non-standard Yes Details →
0.98.8 20 Sep 2017 U1 non-standard Yes Details →
0.98.7 26 Mar 2017 U1 non-standard Yes Details →
0.98.6 28 Dec 2016 U1 non-standard Yes Details →
0.98.5 21 Sep 2015 U2 non-standard Yes Details →
0.98.4 28 Mar 2015 H2 U3 non-standard Yes Details →
0.98.3 25 Feb 2015 H2 U3 non-standard Yes Details →
0.98.2 04 Nov 2014 H2 U3 non-standard Yes Details →
0.98.1 31 Aug 2014 H2 U3 non-standard Yes Details →
0.98.0 29 Jul 2014 H2 U3 non-standard Yes Details →
0.98.0a1 15 Jul 2014 H2 U3 non-standard Yes Details →
0.96.0 30 Nov 2013 H2 U3 GPL-2.0 Yes Details →
0.98.5-py2.7-linux-x86_64 — U2 — Yes Details →
0.98.6-py2.7-linux-x86_64 — U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for admesh

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-38072: ADMesh Heap Buffer Overflow Vulnerability in STL File Processing 8.8 high 5fab257268a0ee6f832c18d72af89810a29fbd5f 03 Apr 2023
CVE-2022-38072: ADMesh Heap Buffer Overflow Due to Improper Array Index Validation 8.8 high 0.98.5 03 Apr 2023
CVE-2018-25033: Out-of-bounds read in admesh 8.1 high 0.98.5 09 May 2022
CVE-2026-2653: Heap-Based Buffer Overflow in admesh up to 0.98.5 7.8 high 0.98.6 18 Feb 2026
CVE-2018-25033: Heap-based Buffer Over-read in admesh N/A unrated 0.98.5 08 May 2022

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 admesh

Is admesh safe to use?

Vulert records 5 vulnerabilities for admesh in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 3 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 admesh's Vulert package health score?

Vulert scores admesh 45/100, which reads as risky. 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 admesh affected?

Yes. 0.98.9, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of admesh should I use?

0.98.9 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 admesh have?

5 vulnerabilities are recorded for admesh in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 3 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 admesh vulnerabilities disclosed?

1 vulnerability was recorded for admesh in the last 12 months, and the oldest entry in this database dates to 08 May 2022. 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 admesh 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 admesh for upcoming vulnerabilities?

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