Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

We’re excited to share that Detectify is one of the vendors featured in KuppingerCole’s Analysts 2026 Leadership Compass on Attack Surface Management. Attack surfaces grow every time a team ships code, opens a port, or points a DNS record to a new service. Keeping track of what’s exposed is hard enough, and knowing which of those exposures an attacker can actually use is harder still.

On October 20, 2026, the PHP security team issued an advance security advisory regarding two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, affecting core PHP source code. Both vulnerabilities carry a critical-severity CVSS v4.0 score of 9.2 and could potentially allow unauthenticated remote code execution (RCE) on affected servers. The official patched PHP releases are now available.

If your application security program only tracks known Common Vulnerabilities and Exposures (CVEs), you’re probably missing a large share of your real risk. Across the Detectify platform, 75% of the vulnerabilities in our test catalog and 99% of those we discover in customers’ assets are non-CVE vulnerabilities. That makes public disclosures a poor measure of coverage on a modern attack surface. Below, we look at why so many vulnerabilities never get a CVE and how Detectify finds both kinds.