Vulnerability Database · PyPI · Package report
types-cffi: vulnerability history, versions and safety
types-cffi is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the PyPI ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on types-cffi 2.1.0.20260827 i
Updated on 23 Oct 2026
Good news: 2.1.0.20260827, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Moderate
What to do: Stay on 2.1.0.20260827 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.0.20260827 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.1.0.20260827 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 146 packages i
- Stars 5,136 i
- OpenSSF scorecard 4/10 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 types-cffi, 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.
- 2.1.0.20260827 27 Aug 2026
- 2.0.0.20260518 18 May 2026
- 2.0.0.20260508 08 May 2026
- 2.0.0.20260506 06 May 2026
- 2.0.0.20260504 04 May 2026
- 2.0.0.20260429 29 Apr 2026
- 2.0.0.20260408 08 Apr 2026
- 2.0.0.20260402 02 Apr 2026
- 2.0.0.20260316 16 Mar 2026
- 2.0.0.20260315 15 Mar 2026
- 1.17.0.20260307 07 Mar 2026
- 1.17.0.20250915 15 Sep 2025
- 1.17.0.20250914 14 Sep 2025
- 1.17.0.20250822 22 Aug 2025
- 1.17.0.20250809 09 Aug 2025
- 1.17.0.20250805 05 Aug 2025
- 1.17.0.20250801 01 Aug 2025
- 1.17.0.20250523 23 May 2025
- 1.17.0.20250516 16 May 2025
- 1.17.0.20250326 26 Mar 2025
- 1.17.0.20250319 19 Mar 2025
- 1.16.0.20250318 18 Mar 2025
- 1.16.0.20250307 07 Mar 2025
- 1.16.0.20241221 21 Dec 2024
- 1.16.0.20240331 31 Mar 2024
- 1.16.0.20240311 11 Mar 2024
- 1.16.0.20240106 06 Jan 2024
- 1.16.0.0 29 Sep 2023
- 1.15.1.15 13 Aug 2023
- 1.15.1.14 04 Jun 2023
- 1.15.1.13 27 Apr 2023
- 1.15.1.12 13 Apr 2023
- 1.15.1.11 06 Apr 2023
- 1.15.1.10 27 Mar 2023
- 1.15.1.9 27 Mar 2023
- 1.15.1.8 23 Mar 2023
- 1.15.1.7 26 Feb 2023
- 1.15.1.6 21 Feb 2023
- 1.15.1.5 07 Feb 2023
- 1.15.1.4 18 Jan 2023
- 1.15.1.3 13 Nov 2022
- 1.15.1.2 09 Nov 2022
- 1.15.1.1 09 Nov 2022
- 1.15.1 27 Sep 2022
- 1.15.0 15 Sep 2022
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 2.1.0.20260827 | 27 Aug 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260518 | 18 May 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260508 | 08 May 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260506 | 06 May 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260504 | 04 May 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260429 | 29 Apr 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260408 | 08 Apr 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260402 | 02 Apr 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260316 | 16 Mar 2026 | none | Apache-2.0 | — | Details → |
| 2.0.0.20260315 | 15 Mar 2026 | none | Apache-2.0 | — | Details → |
| 1.17.0.20260307 | 07 Mar 2026 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250915 | 15 Sep 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250914 | 14 Sep 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250822 | 22 Aug 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250809 | 09 Aug 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250805 | 05 Aug 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250801 | 01 Aug 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250523 | 23 May 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250516 | 16 May 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250326 | 26 Mar 2025 | none | Apache-2.0 | — | Details → |
| 1.17.0.20250319 | 19 Mar 2025 | none | Apache-2.0 | — | Details → |
| 1.16.0.20250318 | 18 Mar 2025 | none | Apache-2.0 | — | Details → |
| 1.16.0.20250307 | 07 Mar 2025 | none | Apache-2.0 | — | Details → |
| 1.16.0.20241221 | 21 Dec 2024 | none | Apache-2.0 | — | Details → |
| 1.16.0.20240331 | 31 Mar 2024 | none | Apache-2.0 | — | Details → |
| 1.16.0.20240311 | 11 Mar 2024 | none | Apache-2.0 | — | Details → |
| 1.16.0.20240106 | 06 Jan 2024 | none | Apache-2.0 | — | Details → |
| 1.16.0.0 | 29 Sep 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.15 | 13 Aug 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.14 | 04 Jun 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.13 | 27 Apr 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.12 | 13 Apr 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.11 | 06 Apr 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.10 | 27 Mar 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.9 | 27 Mar 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.8 | 23 Mar 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.7 | 26 Feb 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.6 | 21 Feb 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.5 | 07 Feb 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.4 | 18 Jan 2023 | none | Apache-2.0 | — | Details → |
| 1.15.1.3 | 13 Nov 2022 | none | Apache-2.0 | — | Details → |
| 1.15.1.2 | 09 Nov 2022 | none | Apache-2.0 | — | Details → |
| 1.15.1.1 | 09 Nov 2022 | none | Apache-2.0 | — | Details → |
| 1.15.1 | 27 Sep 2022 | none | Apache-2.0 | — | Details → |
| 1.15.0 | 15 Sep 2022 | none | Apache-2.0 | — | Details → |
All 45 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for types-cffi
No vulnerabilities match this view.
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
Questions
About types-cffi
Is types-cffi safe to use?
Vulert has no vulnerabilities on record for types-cffi in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is types-cffi's Vulert package health score?
Vulert scores types-cffi 85/100, which reads as healthy. 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 types-cffi affected?
No. 2.1.0.20260827, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of types-cffi should I use?
2.1.0.20260827 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 types-cffi have?
0 vulnerabilities are recorded for types-cffi in the PyPI ecosystem: 0 critical, 0 high, 0 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 types-cffi vulnerabilities disclosed?
0 vulnerabilities were recorded for types-cffi in the last 12 months. 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 types-cffi 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 types-cffi for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the types-cffi version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.