Skip to content

Release Notes

#184 · Escape's AI Pentesting now learns from your false positives

Escape's AI pentesting engine "Cascade" already flags very few false positives. The ones that slip through are almost always context problems, not detection problems: a pattern that looks exploitable everywhere except in your app, for reasons only your team knows.

Now you only have to explain that once.

What's new

When an issue is marked as a false positive, either manually by your team or by Cascade's AI false positive detection, Cascade extracts the underlying pattern and carries it into every future assessment. Triage one instance, and every other issue sharing that vulnerability pattern stops being reported.

How it works

Cascade treats manually-triaged and AI-flagged false positives as the only source of truth for suppression. Nothing else feeds the model, which keeps the blast radius tight and predictable. Pattern extraction happens per assessment target, so business context stays where it belongs. Your triage decisions compound. The tenth assessment costs less review time than the first.

Why it matters

Triage is where continuous security programs slow down. Every repeated "we already looked at this" is time your team spends re-litigating a decision it already made. Cascade now remembers so you don't have to.

Available now for all Cascade assessments. No configuration required.

#183 · wp2shell detection is live (CVE-2026-63030, CVE-2026-60137)

Availability: General Availability

wp2shell is an unauthenticated RCE chain in WordPress core. A REST batch route-confusion flaw (CVE-2026-63030) skips authentication and feeds a SQL injection in WP_Query (CVE-2026-60137). No plugins, no login. It affects WordPress 6.9.0 to 6.9.4 and 7.0.0 to 7.0.1, is already being exploited in the wild, and is fixed in 6.9.5 and 7.0.2.

Escape now detects it across DAST and AI Pentesting. DAST confirms the injection with a time-based oracle instead of guessing from a version string, and AI Pentesting walks the full chain and returns proof of exploitation.

wordpress-vuln-dast.png

Recommended action: connect to your Escape account to verify whether you've been affected, update to 6.9.5 or 7.0.2, and confirm the auto-update actually applied.

We proactively reach out to our current customers who might have been affected by this issue.

See your exposure in one view

  • Open All Issues.
  • Search for "WordPress Core - Pre-Authentication".
  • Save as a new view.

Screenshot 2026-07-21 at 12.23.19.png

You get a live view of every affected asset, with the exposed and unauthenticated counts broken out for triage.

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#182 · One-Click Fix in Cursor: Turn Findings Into Codebase-Tailored Remediation

Availability: General Availability

Escape closes the loop between triage and fix. When you see a finding, you no longer copy details into your IDE and rebuild context from scratch: one click from the issue side panel sends a remediation prompt straight to Cursor, Claude Code, or Codex. The prompt carries your finding so your coding agent starts with everything it needs.

Fix this finding menu on an issue side panel with Open in Cursor, Claude Code, Codex, and Copy as prompt options

What's new:

  • Fix this finding: Start remediation from any issue side panel with a single action.
  • IDE choice: Open in Cursor, Claude Code, Codex, or copy the prompt to your clipboard.
  • Deep links: Cursor opens with the full prompt preloaded through a native deep link.

IDE integrations documentation →

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#181 · ASM now supports large IP ranges

Attack surface discovery can now run across IP ranges up to /16. That's roughly 65,000 addresses in a single scope, which covers most corporate netblocks in one pass instead of splitting them into fragments.

Available on request. Contact your account team or support to enable it for your workspace.

#180 · AI Pentest Reasoning Logs: See Every Step Your AI Pentest Takes

Availability: General Availability

Reasoning Logs give you a live, navigable view of your AI pentest while it runs. You open the agent tree, pick any agent, and read its reasoning, the tools it called, the findings it raised, and how long each step took. Security teams told us they want a full audit trail of what the agent tried, what it skipped, and what it proved. That's what you get now.

image.png

What's new:

  • Live agent tree: the orchestrator and every sub-agent (BOLA, business logic, XSS, SQL injection, and more) appear as a tree you expand and navigate.
  • Full step detail: each agent exposes its reasoning, tool calls, findings count, and run duration, so you follow how one signal escalates into an attack chain.
  • Live during the scan: activity streams in as the pentest runs. You don't wait for the final report to see what's happening.
  • Cleaner and more readable: jump straight to the latest activity, with the noise stripped out so the trace stays easy to follow.

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#179 · First and last login now shown for every member

The org members page now shows a first login and last login column for every member. Screenshot 2026-07-24 at 11.55.05.png

Together they answer the three questions admins actually ask: when did this person activate, are they using the platform consistently, and are they still around?

First login shows an absolute date, like "Jan 12, 2025." Last login shows relative time, like "3 days ago."

At a glance, you can find members who were invited but never logged in, spot accounts that have gone quiet, and check seat usage before a renewal conversation.

Status labels are also simpler now: invited, activated, deactivated.

#178 · AI Pentest profiles now ship with default scope restrictions

Escape's AI Pentesting runs a multi-agent harness that explores your app the way an attacker would. Scope restrictions are how you tell it where not to go. Until now, that list started empty on every new profile, which meant configuring it before the first run, or letting an autonomous agent loose on your app with no guardrails at all.

Now it comes pre-filled.

What's new

scope-ai-pentesting.png

Every new AI Pentest profile now starts with a curated blocklist of URL patterns, covering destructive and sensitive routes like delete, admin, and auth endpoints. It's the same default blocklist behavior DAST profiles have had, now applied to AI Pentesting.

Why it matters

  • A sensible baseline with no configuration. Create a profile, run it, and the obvious foot-guns are already out of scope.
  • Lower risk of accidental damage during a run. Autonomous agents are good at finding paths you didn't think to exclude, which is the point of them and also the problem.

And of course, you can add, remove, or replace patterns as you learn your own app's shape.

Applies to all newly created AI Pentest profiles. Existing profiles are unchanged.

#177 · Critical Severity: Focus on Your Most Urgent Findings First

Availability: General Availability

Your findings now carry a Critical rating, the tier above High. Escape derives Critical from the CVSS score, so your severities line up with the frameworks your remediation cycles already run on. Security teams told us a missing Critical tier kept Escape findings out of their global vulnerability reporting, so this closes that gap and lets you surface what needs attention first.

image.png

What's new:

  • Critical tier: A new top severity above High. The findings that matter most stand out at a glance.
  • CVSS-aligned: Critical is derived from the CVSS score, matching the standard the rest of your stack already uses.
  • High-confidence coverage: Critical appears on AI pentest findings and technology CVEs, where Escape validates before rating a finding Critical.
  • Drives your workflows: Filter, alert, and route Critical findings into Slack, Jira, and your other integrations.

What's next: Critical severity for DAST findings is coming next.

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#176 · Upload any artifact to an AI Pentest

The artifacts step now accepts any file type. OpenAPI specs, Postman collections, prior pentest reports, threat models, archives, images, whatever context you have. No format restrictions to work around before a run.

artifacts.png

Uploaded artifacts are also picked up during review configuration, so the context you provide informs setup, not just the run itself.

#175 · AWS Integration IAM Roles: Connect Accounts Without Long-Lived Access Keys

Availability: General Availability

Escape connects to your AWS accounts through IAM role assumption and an External ID. You grant access with a role trust policy instead of storing long-lived access keys, the same short-lived credential pattern you use for other enterprise SaaS integrations at scale. Add the new AWS integration type from the integrations page; the legacy access-key path stays available.

AWS integration setup form with External ID and role ARN fields

What's new:

  • AWS integration type: Add an integration that authenticates through STS AssumeRole with an External ID instead of static credentials.
  • No long-lived keys: Grant access through a role trust policy instead of static credentials stored in Escape.
  • Legacy path preserved: The existing AWS_ACCOUNT integration (access keys) remains for backward compatibility and is marked as legacy in the UI.

AWS integration documentation →

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.