PostgreSQL vs MySQL
Security track record, side by side · PostgreSQL · Oracle
On tracked security data, MySQL currently has the cleaner record — fewer exploited and high-severity CVEs than PostgreSQL. That reflects history, not a guarantee: always check the exact version you run.
Health score (latest supported)iOur 0–100 score for the newest supported release — higher is healthier. 100/100 100/100
Known CVEs (all time)iTotal tracked CVEs ever recorded. A larger, older, more-scrutinised project tends to have more — context, not a verdict. 209 1328
Actively exploited (CISA KEV)iCVEs confirmed exploited in the wild. The strongest real-world signal — fewer is better. 0 0
Critical CVEsiCVSS 9.0–10.0 across tracked history. 7 7
High CVEsiCVSS 7.0–8.9 across tracked history. 95 75✓
Latest supportediNewest release still receiving fixes. 18.6 26.10.0
How to read this. This compares historical vulnerability track record from NVD and CISA KEV — not code quality, config, or your deployment. A higher CVE count often reflects a larger codebase, longer history and more security research, not necessarily weaker software. The decisive security question is the version you run — so check it.