singular vulnerabilities and fixes
Recent CVEs affecting singular, with upgrade or downgrade steps. 1 tracked.
singular has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2022-09-09. Highest priority: CVE-2022-40299 (score 39/100).
- CVE-2022-40299 HIGH 7.8 UPGRADE In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to g
FAQ
How do I fix singular 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 singular being exploited right now?
None of the tracked singular CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which singular CVE should I patch first?
CVE-2022-40299 currently ranks highest (39/100): In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to g.