Vulert records 6 vulnerabilities for nsmd in OSS-Fuzz: 0 critical, 0 high, 6 medium and 0 low. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does nsmd have?

6 vulnerabilities are recorded for nsmd in the OSS-Fuzz ecosystem: 0 critical, 0 high, 6 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 nsmd vulnerabilities disclosed?

6 vulnerabilities were recorded for nsmd in the last 12 months, and the oldest entry in this database dates to 04 Jul 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 nsmd 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 nsmd for upcoming vulnerabilities?

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

Vulnerability Database · OSS-Fuzz · Package report

nsmd: vulnerability history, versions and safety

nsmd is a package in the OSS-Fuzz ecosystem. Vulert records 6 vulnerabilities for it across 1 affected range, from Jul 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

6 vulnerabilities recorded M6

6 with no fix published

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

See the unfixed vulnerabilities →

6 in the last 12 months

Most recent disclosure 28 Aug 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nsmd vulnerabilities

Vulert verdict on nsmd i

Updated on 23 Oct 2026

Careful: 6 of the 6 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 6 vulnerabilities on record across 1 year, 6 in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

Vulnerabilities on record 6 over 1 year · 6 in the last year i
Latest disclosure 28 Aug 2026 i
Highest CVSS n/a i
With no published fix 6 i

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.

Scan your app free →

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

Affected range	Vulnerabilities
from 62de34e8b8bda9eab592ad737b7fbb3924a55e89 onwards, no fix published yet	6

02 Disclosure history

How often vulnerabilities are recorded

2026 6

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for nsmd

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Heap Buffer Overflow Vulnerability in nsmd Package	N/A medium	No fix published	04 Jul 2026
Heap Buffer Overflow Vulnerability in nsmd Package	N/A medium	No fix published	05 Jul 2026
Heap Buffer Overflow Vulnerability in nsmd Package	N/A medium	No fix published	05 Jul 2026
Heap Buffer Overflow Vulnerability in nsmd Package	N/A medium	No fix published	05 Jul 2026
Heap Buffer Overflow Vulnerability in nsmd Package	N/A medium	No fix published	28 Aug 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