security center vulnerabilities and fixes
Recent CVEs affecting security center, with upgrade or downgrade steps. 5 tracked.
Also searched as: securitycenter.
security center has 5 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 5. Most recent: 2026-07-21. Highest priority: CVE-2026-64879 (score 55/100).
- CVE-2026-64879 CRITICAL 9.9 UPGRADE A filename supplied during file upload is not properly sanitized before being used in system command execution
- CVE-2026-64881 HIGH 8.8 UPGRADE The audit file upload handler does not sanitize filenames, allowing shell metacharacters to flow into system c
- CVE-2026-64878 CRITICAL 9.9 UPGRADE Unvalidated input in asset filter parameters allows shell metacharacters to escape command argument handling,
- CVE-2026-64877 HIGH 8.4 UPGRADE An authenticated non-admin user can exploit a SQL injection flaw in the ticketing REST API to access sensitive
- CVE-2026-64880 HIGH 7.1 UPGRADE Unsanitized user-supplied input in report filtering parameters is concatenated directly into SQL queries witho
FAQ
How do I fix security center 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 security center being exploited right now?
None of the tracked security center CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which security center CVE should I patch first?
CVE-2026-64879 currently ranks highest (55/100): A filename supplied during file upload is not properly sanitized before being used in system command execution.