What is Agent-as-a-Service pentesting?

Agent-as-a-Service (AaaS) pentesting lets you chat with autonomous pentesting agents that scan your application on demand. Instead of waiting weeks for a manual engagement, you talk to specialized agents — pen-scout (recon and surface mapping), pen-recon (deeper enumeration), pen-triage (validates and prioritizes findings), pen-fixer (remediation guidance), and pen-compliance (OWASP/standards mapping). Findings are validated with proof-of-concept and re-test, not just flagged. You start with 150 free credits, no credit card.

What are credits and how do they work?

Credits are how you run agent scans. Each scan or agent action consumes credits based on its depth. New accounts get 150 free credits with no card required. After that you can buy one-time credit packs ($29, $79, or $199) for pay-as-you-go use, or subscribe to a monthly tier ($49, $149, or $399/mo) for continuous, on-demand pentesting. The agents pen-scout, pen-recon, pen-triage, pen-fixer and pen-compliance all draw from the same credit balance.

Yes. Every new account gets 150 free credits with no credit card required — enough to chat with the pentesting agents and run real scans against your app. There is also a free security headers scan at sable.somoswilab.com/free-scan and a sample report at sable.somoswilab.com/sample-report. The free tier runs on OpenRouter models so you can evaluate the autonomous agents before paying.

What is penetration testing for startups?

Penetration testing (pentesting) is a simulated cyberattack against your application to find security vulnerabilities before real attackers do. For startups, we focus on the issues that matter most at your stage: authentication flaws, data exposure, API security, and common mistakes in modern stacks like Next.js, Supabase, and Firebase.

How much does a pentest cost?

Traditional pentests cost $10,000-$50,000+. SableOffensive starts at $29 for a Pre-Launch Check covering OWASP Top 10 and secrets detection. Founder Shield ($79) adds IDOR testing, auth bypass, and a debrief call. Scale Secure ($199) is a full-scope assessment. Every plan includes a professional report with remediation steps.

How long does a security scan take?

Pre-Launch Check reports are delivered within 24-48 hours. Founder Shield and Scale Secure may take 2-3 business days depending on the complexity of your application.

What do I need to provide?

At minimum, just your application URL. For more comprehensive testing, we may ask for staging credentials, API documentation, or GitHub repository access. We sign NDAs for all engagements.

What is OWASP Top 10?

OWASP Top 10 is the industry standard list of the most critical web application security risks. It includes injection attacks, broken authentication, cross-site scripting (XSS), server-side request forgery (SSRF), and security misconfigurations. Every SableOffensive assessment tests against the full OWASP Top 10.

Do you test AI-generated code?

Yes. Code generated by AI tools like Cursor, GitHub Copilot, and v0 often contains subtle security issues: hardcoded secrets, missing input validation, insecure API patterns, and overly permissive access controls. We have specific testing procedures for AI-generated codebases.

How do you secure Supabase and Firebase apps?

For Supabase, we audit Row Level Security (RLS) policies, test for direct table access, and check for exposed service keys. For Firebase, we review security rules, test Firestore/RTDB access patterns, and check Cloud Functions for vulnerabilities.

What if you find zero vulnerabilities?

50% money back guarantee. If our scan finds zero security issues, you get half your money back.

Is there a free pentesting option?

Yes. SableOffensive offers a free security headers scan at sable.somoswilab.com/free-scan. It instantly checks your website for 8 critical security headers (HSTS, CSP, X-Frame-Options, and more) and gives you an A-F grade with copy-paste fixes. No signup or payment required.

Can I get a free vulnerability scan?

Our free security headers check scans your website instantly and grades your security posture. For a deeper free assessment, contact us — we occasionally offer complimentary scans for early-stage startups and open source projects.

Critical Ruflo MCP Bridge Vulnerability (CVE-2026-59726) Allows Remote Code Execution

What Happened

On 29 July 2026 security researchers at Noma Labs disclosed a critical vulnerability in the open‑source AI orchestration platform Ruflo. The flaw, tracked as CVE‑2026‑59726 with a CVSS base score of 10.0, allows an unauthenticated attacker to execute arbitrary commands via Ruflo’s Model Context Protocol (MCP) bridge.[The Hacker News]

Technical Analysis

Ruflo’s MCP bridge is implemented as an Express.js HTTP server that proxies 233 tool calls, including ruflo__terminal_execute for shell commands. By default the Docker‑compose configuration binds the bridge to 0.0.0.0:3001, exposing the endpoint to any network‑reachable host. An attacker can send a single JSON‑RPC POST request to /mcp that invokes tools/call with ruflo__terminal_execute, granting immediate shell access inside the container. The researchers demonstrated a curl command that retrieves system identity information and reads environment variables, exposing API keys for LLM providers and internal MongoDB credentials.[HackRead] The vulnerability impacts all Ruflo versions prior to 3.16.3, the version that introduced secure defaults.[CyberSecurityNews]

Who’s Affected

Any organization deploying Ruflo with the default Docker‑compose file before version 3.16.3 is vulnerable. Because Ruflo is widely adopted for AI‑agent swarms, the attack surface includes enterprises that use the platform for autonomous workflow orchestration, code generation (Claude Code, OpenAI Codex), or any AI‑driven automation. The exposed MCP bridge also provides a path to steal LLM API keys, potentially enabling attackers to consume paid credits or hijack downstream AI services. Large‑scale deployments that expose port 3001 to the internet without firewall restrictions are at highest risk.

How to Protect Yourself

Update Ruflo immediately to version 3.16.3 or later, which binds the MCP bridge to 127.0.0.1 by default.
If you must expose the bridge, enforce strict bearer‑token authentication and restrict network access with firewall rules (allow only trusted internal subnets).
Rotate all LLM provider API keys and any secrets stored in environment variables as soon as possible.
Audit your Docker‑compose files: ensure the ports section for the MCP bridge is removed or bound to localhost.
Review the AgentDB memory store for unauthorized entries; delete any suspicious patterns that could influence future AI responses.

The Sable Angle

At Sable we routinely assess AI‑agent pipelines for supply‑chain exposure. Our offensive research team has built custom tools to probe MCP‑exposed services and demonstrate how quickly an attacker can pivot from a single shell command to full‑cluster compromise. By integrating the lessons from CVE‑2026‑59726 into our hardening guides, we help customers secure their AI workloads while preserving the agility that Ruflo provides. Learn more about our AI‑security services at Sable AI Agent Hardening and explore our managed monitoring solution at Sable Pricing.