Vulnerability Database · PyPI · Package report
osqp: vulnerability history, versions and safety
osqp 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 osqp 1.1.3 i
Updated on 23 Oct 2026
Good news: 1.1.3, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Widely used
- Community Not enough data
What to do: Stay on 1.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 785 packages i
- Last release 4 months 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 osqp, 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.
- 1.1.3 12 Jun 2026
- 1.1.2 09 Jun 2026
- 1.1.1 11 Feb 2026
- 1.1.0 26 Jan 2026
- 1.0.5 15 Oct 2025
- 1.0.4 08 May 2025
- 1.0.3 02 Apr 2025
- 1.0.2 01 Apr 2025
- 1.0.1 25 Mar 2025
- 1.0.0 23 Mar 2025
- 1.0.0b4 14 Mar 2025
- 1.0.0b3 13 Feb 2025
- 0.6.7.post3 11 Oct 2024
- 0.6.7.post2 10 Oct 2024
- 0.6.7.post1 23 Jul 2024
- 0.6.7.post0 25 Jun 2024
- 0.6.7 22 May 2024
- 0.6.6 22 May 2024
- 0.6.5 05 Feb 2024
- 0.6.4 03 Feb 2024
- 1.0.0b1 01 Jun 2023
- 0.6.3 26 May 2023
- 0.6.2.post9 14 Apr 2023
- 0.6.2.post8 22 Nov 2022
- 0.6.2.post5 07 Jan 2022
- 0.6.2.post4 28 Dec 2021
- 0.6.2.post3 28 Dec 2021
- 0.6.2.post2 28 Dec 2021
- 0.0.0 28 Dec 2021
- 0.6.2.post1 28 Dec 2021
- 0.6.2.post0 14 Jan 2021
- 0.6.2 06 Jan 2021
- 0.6.1 07 May 2020
- 0.6.0 31 Aug 2019
- 0.5.0 11 Dec 2018
- 0.4.1 27 Sep 2018
- 0.4.0 27 Jul 2018
- 0.3.0 05 Mar 2018
- 0.2.1 25 Nov 2017
- 0.2.0 24 Nov 2017
- 0.1.3 21 Sep 2017
- 0.1.1
- 0.1.1-py2.7-macosx-10.7-x86_64
- 0.1.1-py2.7-win-amd64
- 0.1.1-py2.7-win32
- 0.1.1-py3.5-macosx-10.7-x86_64
- 0.1.1-py3.5-win-amd64
- 0.1.1-py3.5-win32
- 0.1.1-py3.6-macosx-10.7-x86_64
- 0.1.1-py3.6-win-amd64
- 0.1.1-py3.6-win32
- 0.1.2
- 0.1.2-py2.7-macosx-10.7-x86_64
- 0.1.2-py2.7-win-amd64
- 0.1.2-py2.7-win32
- 0.1.2-py3.5-macosx-10.7-x86_64
- 0.1.2-py3.5-win-amd64
- 0.1.2-py3.5-win32
- 0.1.2-py3.6-macosx-10.7-x86_64
- 0.1.2-py3.6-win-amd64
- 0.1.2-py3.6-win32
- 0.1.3-py2.7-macosx-10.7-x86_64
- 0.1.3-py2.7-win-amd64
- 0.1.3-py2.7-win32
- 0.1.3-py3.5-macosx-10.7-x86_64
- 0.1.3-py3.5-win-amd64
- 0.1.3-py3.5-win32
- 0.1.3-py3.6-linux-x86_64
- 0.1.3-py3.6-macosx-10.7-x86_64
- 0.1.3-py3.6-win-amd64
- 0.1.3-py3.6-win32
- 0.2.0-py2.7-win-amd64
- 0.2.0-py2.7-win32
- 0.2.0-py3.5-win-amd64
- 0.2.0-py3.5-win32
- 0.2.0-py3.6-win-amd64
- 0.2.0-py3.6-win32
- 0.2.1-py2.7-macosx-10.6-x86_64
- 0.2.1-py2.7-win-amd64
- 0.2.1-py2.7-win32
- 0.2.1-py3.5-macosx-10.6-x86_64
- 0.2.1-py3.5-win-amd64
- 0.2.1-py3.5-win32
- 0.2.1-py3.6-linux-x86_64
- 0.2.1-py3.6-macosx-10.7-x86_64
- 0.2.1-py3.6-win-amd64
- 0.2.1-py3.6-win32
- 0.3.0-py2.7-macosx-10.6-x86_64
- 0.3.0-py2.7-win-amd64
- 0.3.0-py2.7-win32
- 0.3.0-py3.5-macosx-10.6-x86_64
- 0.3.0-py3.5-win-amd64
- 0.3.0-py3.5-win32
- 0.3.0-py3.6-linux-x86_64
- 0.3.0-py3.6-macosx-10.7-x86_64
- 0.3.0-py3.6-win-amd64
- 0.3.0-py3.6-win32
- 0.3.1
- 0.6.0.dev18
- 1.0.0a1
- 1.0.0a3
All 101 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 osqp
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 osqp
Is osqp safe to use?
Vulert has no vulnerabilities on record for osqp 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 osqp's Vulert package health score?
Vulert scores osqp 90/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 osqp affected?
No. 1.1.3, 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 osqp should I use?
1.1.3 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 osqp have?
0 vulnerabilities are recorded for osqp 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 osqp vulnerabilities disclosed?
0 vulnerabilities were recorded for osqp 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 osqp 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 osqp for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the osqp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.