Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

cuyahoga vulnerabilities and fixes

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

cuyahoga has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2007-01-09. Highest priority: CVE-2007-0147 (score 35/100).

FAQ

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

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

Which cuyahoga CVE should I patch first?

CVE-2007-0147 currently ranks highest (35/100): Cuyahoga before 1.0.1 installs the FCKEditor component with an incorrect deny statement in a Web.config file, .

← Back to latest CVEs