How many known CVEs do Nginx and Traefik have?

In our tracked data, Nginx has 2 known CVEs (1 actively exploited) and Traefik has 54 (1 actively exploited).

Nginx vs Traefik

Q: Is Nginx or Traefik more secure?

Nginx: score 100/100, 2 known CVEs (1 actively exploited, 0 critical). Traefik: score 0/100, 54 known CVEs (1 actively exploited, 15 critical). On tracked security data, Nginx currently has the cleaner record — fewer exploited and high-severity CVEs than Traefik. That reflects history, not a guarantee: always check the exact version you run.

Security track record, side by side · Nginx / F5 · Traefik Labs

On tracked security data, Nginx currently has the cleaner record — fewer exploited and high-severity CVEs than Traefik. That reflects history, not a guarantee: always check the exact version you run.

NginxNginx / F5 TraefikTraefik Labs

Health score (latest supported)iOur 0–100 score for the newest supported release — higher is healthier. 100/100✓ 0/100

Known CVEs (all time)iTotal tracked CVEs ever recorded. A larger, older, more-scrutinised project tends to have more — context, not a verdict. 2 54

Actively exploited (CISA KEV)iCVEs confirmed exploited in the wild. The strongest real-world signal — fewer is better. 1 1

Critical CVEsiCVSS 9.0–10.0 across tracked history. 0✓ 15

High CVEsiCVSS 7.0–8.9 across tracked history. 2✓ 28

Latest supportediNewest release still receiving fixes. 1.31.3 —

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.

Check your exact version → Nginx status Traefik status