Was tikv-jemalloc-ctl Hacked?

No Publicly Reported Incidents. As of April 2026, tikv-jemalloc-ctl 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 tikv-jemalloc-ctl's security posture as strong (security dimension score: 90/100). Trust Score: 63/100 (C+). Last checked: 2026-04-18.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score63/100 (C+)
Security Dimension90/100
PublisherUnknown
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see tikv-jemalloc-ctl Trust Score on Nerq.

FAQ

Has tikv-jemalloc-ctl been hacked?
As of April 2026, tikv-jemalloc-ctl 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 tikv-jemalloc-ctl have?
tikv-jemalloc-ctl has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is tikv-jemalloc-ctl safe to use after a breach?
With no reported breaches, tikv-jemalloc-ctl appears safe based on available data.
Where can I check tikv-jemalloc-ctl's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for tikv-jemalloc-ctl. View the full trust analysis at nerq.ai/safe/tikv-jemalloc-ctl.

Updated April 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy