The Blind Spots of Agentic Pentesting and How to Close Them
Picus says agentic pentesting misses unreachable assets and flaws that lack safe exploits.
A Picus Security research engineer argues that agentic penetration testing is creative but inconsistent, token-expensive, and limited to assets it can safely reach. Omdia found organizations pentest about 32% of their attack surface, while safety and segmentation leave critical or isolated systems untested. In one customer environment, scanners found nginx-ui authentication bypass CVE-2026-33032 on 480 instances, but agentic testing could assess only 120 and confirmed 80 exploitable. VulnCheck reported that only about a quarter of 2025 CVEs had proof-of-concept code, so Picus advocates control-based exploitability validation alongside deterministic and agentic testing.
- Agentic tests can only reach assets that are safe and network-accessible.
- In one case, 360 of 480 nginx-ui instances were out of scope.
- VulnCheck says about a quarter of 2025 CVEs had public exploit details.
- Picus recommends pairing frequent deterministic tests with periodic agentic runs.
- CVEs
- CVE-2026-33032
- Vendors
- Picus Security
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-33032 | Unauthenticated MCP Endpoint Access in Nginx UI Enables Full Nginx Server Takeover | 9.8 | 35% | PoC |
From the original article
6 min read at bleepingcomputer.com
AI-powered penetration testing can uncover complex attack paths, but safety restrictions and network limitations leave many assets and vulnerabilities untested. Picus Security explains how combining agentic pentesting with exposure validation and breach simulation can help close these gaps. [...]
By Sponsored by Picus Security · bleepingcomputer.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.