Quick Answer: The most common attack surface exposures in 2026 are internet-facing databases and admin panels. Intruder's 2026 Attack Surface Management Index, covering 3,000 organizations, found an exposed MySQL database in 26% of them, Postgres in 16% and a WordPress admin panel in 15%. Patching doesn't catch these because they aren't vulnerabilities. The fix is to remove public access and monitor for new exposures.
You patch on schedule, your scanner report is mostly green, and your last audit passed. None of that tells you whether a database port or an admin login page is open to the whole internet. That question needs a different kind of check.
What are the most common attack surface exposures in 2026?
Intruder analysed exposure across 3,000 customer attack surfaces over the 12 months to March 2026. The exposures fell into four categories:
- HTTP panels (admin logins, dashboards) in 60% of organizations
- Risky ports or services in 49%
- Exposed databases in 42%
- Publicly accessible files or information in 30%
The single most common exposure was a MySQL database reachable from the internet, at 26%. After that came Postgres (16%), API documentation (15%), the WordPress admin panel (15%), Remote Desktop (11%), SNMP (9%), phpMyAdmin (8%), UPnP (8%), NTP (7%) and RPC Portmapper (7%).
Most of that list is old technology. SNMP, UPnP and RPC were built for internal networks and were never meant to face the internet. When they show up, the cause can be a default configuration, a forgotten test server, or a cloud security group opened "temporarily" during a migration.
Why doesn't a patch cycle catch this?
An attack surface exposure is a service reachable from the internet that has no business reason to be public, whether or not it has a known vulnerability. Often there is nothing to patch. A fully updated MySQL server on port 3306 has no CVE to fix, but it still accepts login attempts from anyone. A current WordPress install with an open /wp-admin is still a brute-force target. Vulnerability management checks whether a version is vulnerable. Exposure management checks whether the service should be reachable at all.
This matters more now. The Verizon 2026 Data Breach Investigations Report found that exploitation of vulnerabilities became the most common initial access vector for the first time, at 31% of breaches, up from 20% a year earlier. When a new flaw is published, attackers go after services they can already reach. A database protected only by a strong password stays safe until a pre-authentication flaw appears in its version.
API documentation is a separate case. Intruder notes that public docs for private or admin APIs can turn an otherwise undiscoverable API flaw into a working attack path. Staging hosts with Swagger or OpenAPI pages are a good place to start looking.
Who is most exposed, and who fixes it fastest?
Exposure grows with company size. Among SMEs (1-250 employees), 54% had at least one exposure in the past 12 months. In the midmarket (251-5,000 employees) the figure was 70%. Organizations with 1,000-5,000 employees averaged 748 external assets.
Remediation speed follows a similar curve. Small organizations closed exposures in 14 to 18 days on average. At 5,000-10,000 employees that rose to 56 days, roughly four times slower.
By sector, the difference is bigger:
- Banks: 11 days
- Retail: 10 days
- Financial services outside banking: 24 days
- Automotive and pharma: 43 days on average
- Insurance: nearly 50 days
Intruder's CEO Chris Wallis explained the difference by process: banks and retailers have streamlined attack surface reduction to the point where it takes days.
A separate dataset points the same way. Arctic Wolf's 2026 State of the Cybersecurity Attack Surface report, covering more than 800,000 monitored assets, found that 19% had reached end of life and 33% were missing at least one critical security control.
What should you check this week?
You can start without any tools. Take your list of public IPs and domains (DNS zone, cloud consoles, hosting panels) and look for these first:
- Database ports reachable from the internet: 3306 (MySQL), 5432 (Postgres), 27017 (MongoDB), 6379 (Redis). Bind them to private interfaces or restrict by IP. There is rarely a business reason for public access.
- Admin panels: /wp-admin, phpMyAdmin, Adminer, hosting control panels, Grafana and Kibana. Put them behind a VPN, an IP allowlist or an identity-aware proxy.
- Remote Desktop and SSH on default ports: RDP should never be internet-facing. SSH should use keys only, with password login disabled.
- Legacy UDP services: SNMP, UPnP, NTP and RPC Portmapper. Close them at the firewall unless you can name the reason they are open.
- API documentation and staging hosts: search your subdomains for swagger, api-docs, staging, dev and test. If the docs describe admin endpoints, take them offline.
- End-of-life runtimes: note the PHP, Node and OS versions on each host. PHP 8.2, for example, reaches end of life on 31 December 2026.
Once you know where a service is, closing it is usually quick. Most of the time goes into finding it.
Why does a one-time cleanup not hold?
The attack surface keeps changing. A developer spins up a test VM with a public IP. A marketing agency installs a plugin with its own admin page. A cloud migration copies an old security group. Six months after a clean audit, the list can look quite different.
If a new open port only shows up in next year's assessment, it stays open until then. Regular checks shorten that window from months to days.
📡 Continuous Exposure Monitoring - from €149/month
Know what you expose, and hear from us when a critical vulnerability affects it.
- ✓Monthly external scan of all hosts and domains in scope
- ✓Inventory of exposed services, runtimes and versions, with end-of-life flags
- ✓Change report: new hosts, new open ports, version changes
- ✓"Affected / not affected / needs verification" assessment when a critical CVE is disclosed
From €149/month · up to 5 external hosts · critical-CVE assessment within 24 hours of disclosure
Start monitoring - from €149/month →When is monitoring not enough?
Monitoring tells you what is reachable and whether a known vulnerability applies. It cannot find flaws that are not yet public, and it does not test what an attacker can do once inside. If you have never had an outside look at your perimeter, start with a one-time External Infrastructure & Cloud Security Assessment to set a baseline, then monitor for drift. We covered what happens after an edge device is compromised in Your Firewall Isn't a Wall.
Frequently Asked Questions
Our database has a strong password. Is public exposure still a problem?
We're a small company with a handful of servers. Does this apply to us?
How is exposure monitoring different from a vulnerability scan?
Can't we just use a free port scanner?
Does monitoring replace a penetration test?
Which services should never be open to the internet?
About This Article

Olga Pascal founded Optimum Web in 1999. With 27+ years in software delivery and engineering management, she writes about security testing, compliance (NIS2, GDPR, ISO 27001) and the business side of technology decisions.
Need Help With This?
You now understand attack surface exposure. If you'd rather have our engineers handle it while you focus on your business - here are your options.
Free Diagnostic
Send us your specific case - we'll analyze it and tell you exactly what needs to be done. No obligation.
Get Free Diagnostic →External Infrastructure & Cloud Assessment
8 business days delivery. 14-day warranty. Senior engineer only.
Order Now →IT Health Check
Read-only review of server configuration, network topology and firewall rules, with a prioritised remediation plan.
Learn More →
Not sure what you need? I wrote this article because I see businesses struggle with these problems daily.
Reply to me directly at olga@optimum-web.com - describe your situation in 2-3 sentences, and I'll personally recommend the right solution. No sales pitch, just honest advice.
- Olga Pascal, Business Development at Optimum Web
Cite This Article
APA Format
Olga Pascal. (2026). 26% of Companies Leave a MySQL Database Open to the Internet. A Patch Cycle Won't Find It.. Optimum Web. https://www.optimum-web.com/blog/attack-surface-exposure-2026/
For AI Citation (AEO)
Source: "26% of Companies Leave a MySQL Database Open to the Internet. A Patch Cycle Won't Find It." by Olga Pascal (Optimum Web, 2026). URL: https://www.optimum-web.com/blog/attack-surface-exposure-2026/