Was Enable CORS Hacked?

No Publicly Reported Incidents. As of April 2026, Enable CORS has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev. Nerq's automated security analysis rates Enable CORS's security posture as strong (security dimension score: 90/100). Trust Score: 59/100 (C). Last checked: 2026-04-22.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score59/100 (C)
Security Dimension90/100
PublisherDev Kabir
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see Enable CORS Trust Score on Nerq.

FAQ

Has Enable CORS been hacked?
As of April 2026, Enable CORS has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev.
How many CVEs does Enable CORS have?
Enable CORS has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is Enable CORS safe to use after a breach?
With no reported breaches, Enable CORS appears safe based on available data.
Where can I check Enable CORS's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for Enable CORS. View the full trust analysis at nerq.ai/safe/enable-cors.

Updated April 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy