Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

privategpt vulnerabilities and fixes

Recent CVEs affecting privategpt, with upgrade or downgrade steps. 8 tracked.

privategpt has 8 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2025-05-10. Highest priority: CVE-2024-4343 (score 69/100).

FAQ

How do I fix privategpt vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is privategpt being exploited right now?

None of the tracked privategpt CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which privategpt CVE should I patch first?

CVE-2024-4343 currently ranks highest (69/100): A Python command injection vulnerability exists in the `SagemakerLLM` class's `complete()` method within `./pr.

RSS feed for privategpt · ← Back to latest CVEs