Vulnerability Database · PyPI · testingpy · Version
testingpy 0.1.3
0.1.3 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Database updated 23/Oct/2026
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
testingpy 0.1.3 vulnerabilities
1 vulnerability cover testingpy 0.1.3. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Malicious Code Injection in testingpy: A Serious Threat to Users | N/A critical | No fix published | 06 Jan 2026 |
Looking for another version, or everything Vulert holds for testingpy?
Questions
About testingpy 0.1.3
Is testingpy 0.1.3 vulnerable?
Yes. 1 vulnerability in the Vulert database cover testingpy 0.1.3: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
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 testingpy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the testingpy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.