Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

stringbuilder vulnerabilities and fixes

Recent CVEs affecting stringbuilder, with upgrade or downgrade steps. 1 tracked.

stringbuilder has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2024-07-10. Highest priority: CVE-2024-21524 (score 53/100).

FAQ

How do I fix stringbuilder 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 stringbuilder being exploited right now?

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

Which stringbuilder CVE should I patch first?

CVE-2024-21524 currently ranks highest (53/100): All versions of the package node-stringbuilder are vulnerable to Out-of-bounds Read due to incorrect memory le.

← Back to latest CVEs