Skip to content
Automated Vulnerability Remediation

Maze: what it is, what it does well and where it is limited

What it fixes itself
None found on 10 Nov 2026vendor states it validates fixes and suggests mitigations
Who approves
Customer's team controls what gets merged
Resolves the owner
Yes: infers owner from commit history and code
Scanners it reads
Customer's existing scanners by API (none named)
Price
None found on 10 Nov 2026 (vendor prices by cloud size)

Maze: 37 fact lines read

0 third-party 33 vendor's claims 4 none found

What it is

Agentic vulnerability investigation and remediation (code and cloud).

What it does well

Maze defines exploitable as exploitable given the specific configuration, controls and context of the customer's environment, and routes validated fixes, with the investigation behind them, to the owning developer or coding agent for human review.

Where it is limited

Maze quotes pricing by cloud size without a public price list; none found on 10 Nov 2026: customer-built agents, owner follow-up or SLA tracking, a named integration list, or funding and headcount.

Facts read, by topic

Each line below carries a label, the page it was read on and the date. A vendor's claim is the vendor's own statement about itself; a third-party source is one that is not the vendor; a line that starts with none found says nothing was published on that date. Maze has 37 lines on file, read up to 10 Nov 2026; the Maze pages behind them are listed under Sources.

Proves exploitability in your environment

  • Vendor's claim: Maze defines exploitable relative to the customer's own configuration, controls and context, not CVSS or exploit-in-the-wild status. (source, read 10 Nov 2026)
  • Vendor's claim: Every recommendation is said to carry the evidence and reasoning behind it. (source, read 10 Nov 2026)
  • Vendor's claim: Maze says 90% of vulnerabilities it analyzes are not exploitable when investigated. (source, read 10 Nov 2026)
  • Vendor's claim: Runtime context is gathered without installing sensors. (source, read 10 Nov 2026)
  • Vendor's claim: Maze Code decides exploitability in the customer's environment, not only reachability. (source, read 10 Nov 2026)
  • Vendor's claim: In the Cohere Health story, 51% of findings were judged not exploitable and each decision, including closed ones, came with evidence. (source, read 10 Nov 2026)

Ships the fix

  • Vendor's claim: Agents verify that a fix resolves the vulnerability without introducing new ones. (source, read 10 Nov 2026)
  • Vendor's claim: Maze generates and validates fixes but the customer's team controls what gets merged. (source, read 10 Nov 2026)
  • Vendor's claim: Where patching is not possible, Maze suggests mitigations that break the exploitability chain. (source, read 10 Nov 2026)
  • Vendor's claim: Agents bundle proven-exploitable CVEs into single fixes, so one ticket can close 30 or more. (source, read 10 Nov 2026)
  • Vendor's claim: Agents offer several fix options rather than one textbook fix. (source, read 10 Nov 2026)

Finds the owner

  • Vendor's claim: Agents infer the owner from commit history and code, then route the fix to the developer or coding agent. (source, read 10 Nov 2026)
  • Vendor's claim: Fixes are delivered into ticketing platforms or coding agents (Slack or Teams optional). (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: Follow-up after routing (reminders, SLA tracking, escalation): none found on 2026-11-10: owner follow-up or SLA tracking on remediation, platform/cloud and platform/code pages (source, read 10 Nov 2026)

Speed on a new disclosure

  • Vendor's claim: Maze says agents sweep every instance for a new zero-day in hours, before scanners have a signature. (source, read 10 Nov 2026)
  • Vendor's claim: Maze claims agents recognize zero-day vulnerabilities and triage them before scanners see them. (source, read 10 Nov 2026)
  • Vendor's claim: Maze published a response write-up on PHP2Shell dated Oct 22, 2026, one day after the Oct 21 patch release. (source, read 10 Nov 2026)

Agents you can shape

  • Vendor's claim: Maze Cloud and Maze Code are agent-driven products; AI-SCA and AI-SAST are named agent modules. (source, read 10 Nov 2026)
  • Vendor's claim: Vendor-built agents run on custom infrastructure, trained on domain tasks and checked by multiple validation layers. (source, read 10 Nov 2026)
  • Vendor's claim: Maze integrates with coding agents such as Claude and Cursor. (source, read 10 Nov 2026)
  • Vendor's claim: Data control: Maze does not train or fine-tune the underlying models on customer code or findings; single-tenant hosting is offered. (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: Customer-built agents: none found on 2026-11-10: an agent builder or custom-agent feature on mazehq.com platform pages (source, read 10 Nov 2026)

Works on the stack you have

  • Vendor's claim: Maze needs a read-only cloud role and an API connection to vulnerability scanners. (source, read 10 Nov 2026)
  • Vendor's claim: It pulls and deduplicates findings from existing scanners. (source, read 10 Nov 2026)
  • Vendor's claim: The Cohere Health story lists AWS and containers as the environment. (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: Specific scanner, code host and ticketing product names: none found on 2026-11-10: a named integration list on mazehq.com (the FAQ says only that it connects to the scanners customers already have) (source, read 10 Nov 2026)

Proof

  • Vendor's claim: Cohere Health story: 92% of critical and high findings not exploitable, downgraded or remediated. (source, read 10 Nov 2026)
  • Vendor's claim: Same story: 87% of critical and high findings were not exploitable or safe to deprioritize. (source, read 10 Nov 2026)
  • Vendor's claim: Named customer quotes: Alloy, Cohere Health, Forge, PartsSource. (source, read 10 Nov 2026)
  • Vendor's claim: Maze claims deployment by multiple Fortune 100 organizations. (source, read 10 Nov 2026)
  • Vendor's claim: Maze publishes vulnerability research posts, for example a Langfuse SSO bug found by Maze Code. (source, read 10 Nov 2026)

Profile facts

  • Vendor's claim: Maze was started in 2024. (source, read 10 Nov 2026)
  • Vendor's claim: Pricing is based on the size of the customer's cloud infrastructure; no public price list. (source, read 10 Nov 2026)
  • Vendor's claim: Certifications: ISO 27001 and SOC 2 Type II. (source, read 10 Nov 2026)
  • Vendor's claim: Hosted in AWS with multi-tenant or single-tenant options. (source, read 10 Nov 2026)
  • Vendor's claim: Maze says it fits no existing category (CTEM, RBVM, UVM, RemOps, ASPM). (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: Funding, HQ, headcount and founders' names: none found on 2026-11-10: funding, HQ, headcount, founder names on home, our-story, platform pages (source, read 10 Nov 2026)

Sources

8 sources, each with its read date
  1. Maze: mazehq.com/platform/cloud, read 10 Nov 2026
  2. Maze: mazehq.com/, read 10 Nov 2026
  3. Maze: mazehq.com/platform/code, read 10 Nov 2026
  4. Maze: mazehq.com/customer-story/how-cohere-health-cleared-92-of-its-critical-and-high-, read 10 Nov 2026
  5. Maze: mazehq.com/solutions/remediation, read 10 Nov 2026
  6. Maze: mazehq.com/blog/php2shell, read 10 Nov 2026
  7. Maze: mazehq.com/platform, read 10 Nov 2026
  8. Maze: mazehq.com/our-story, read 10 Nov 2026

Last reviewed 10 Nov 2026.