Vulnerability Database · PyPI · python-libnmap · Version

python-libnmap 0.2.7

0.2.7 is affected by 4 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.7.3.

Critical 1 High 1 Medium 0 Low 0 Unrated 2

Released 10 Jun 2013 Licence non-standard Also known from other sources 4 Newer releases 15 Database updated 23/Oct/2026

Release and licence data published by PyPI. 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 Vulnerabilities affecting this version

python-libnmap 0.2.7 vulnerabilities

4 vulnerabilities cover python-libnmap 0.2.7. Open the full list in the database.

Looking for another version, or everything Vulert holds for python-libnmap?

All versions → Full vulnerability list →

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 python-libnmap 0.2.7

Is python-libnmap 0.2.7 vulnerable?

Yes. 4 vulnerabilities in the Vulert database cover python-libnmap 0.2.7: 1 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is 0.7.3, and each entry above names the fixed version to move to.

Which version of python-libnmap should I use instead of 0.2.7?

0.7.3 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 0.2.7 the latest release of python-libnmap?

No. 0.2.7 was published 10 Jun 2013, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor python-libnmap for upcoming vulnerabilities?

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