FARADAI CHANGELOG

Built to evolve

Follow the latest capabilities, improvements and integrations shaping FaradAI.

2026

v4.3.0

Latest release

From finding to fix.

203 improvements shipped in this release. The headline: triage now ends in a pull request, not a ticket.

46Patching & triage
22Wizard & dashboard
16Scan engine & models
New feature

Patch Plans now open pull requests

Triage no longer stops at the finding. FaradAI proposes the fix, opens it as a pull request on GitHub or a merge request on GitLab, and re-tests automatically once it’s merged.

See details
  • Pull requests on GitHub and merge requests on GitLab, generated straight from the Patch Plan.
  • Requests that run into merge conflicts are regenerated from the Patch Plan instead of being fixed by hand.
  • Cached plans that fall out of date are rebuilt automatically.
  • Work that needs a person, like rotating a secret, shows up as a manual item you can mark as fixed.
  • Fixes are generated in the background, grouped by finding type.
  • Repository clone tokens are used for the job and never stored.
New feature

Cloud Security Review for AWS

A new scan type that audits the security posture of your AWS account. It runs Prowler with read-only credentials, validates every finding and has an analyst agent prioritize what matters.

See details
  • A new Cloud access step in the launch wizard connects your account with read-only credentials.
  • Findings are normalized and validated with deterministic checks before any AI analysis.
  • Analysis runs in batches through an agent limited to a restricted set of tools.
New feature

faradai-scan: pentests from your own machine

A command-line client for operators. Register with an email code, scan internal networks through a VPN tunnel and send the engagement bundle to your workspace.

See details
  • Self-registration with a one-time email code. Public email providers aren’t accepted.
  • New registrations get the pentester role and a dedicated workspace.
  • Launch DAST and SAST from faraday-cli inside your pipeline, using pipeline credentials.
Integration

MCP gateway with zero setup

Connect your assistant or agent to FaradAI over MCP without installing anything. The gateway runs on your FaradAI URL, so there’s no extra subdomain or package to manage.

See details
  • Pick HTTP Gateway in the MCP settings to get a configuration that’s ready to paste.
  • Launch scans from MCP or the API with a full-access token.
Integration

Fix DNS findings in your cloud provider

FaradAI can now correct DNS and configuration findings where they live: Vercel, DigitalOcean and AWS Route 53, through a cross-account IAM role.

Improvement

Scheduled scans skip when nothing changed

Recurring scans check the repository first and skip the run when the code hasn’t changed. Run now works on every schedule, and Edit & re-launch is back.

Improvement

A clearer launch wizard and dashboard

Scan completion emails link straight to the report, and the IP allowlist step shows the live egress IPs you need to approve.

See details
  • Read-only access tokens, with an email warning before they expire.
  • Fill with AI shows its progress and grounds suggestions in your source code.

More improvements & fixes

  • Improvement
    One fixed egress IP for every target

    All pentest traffic leaves from a single fixed IP, so allowlisting FaradAI takes one rule. Existing allowlists keep working until you add it.

  • Improvement
    SSO parity and stricter credential handling

    SSO admins get the full admin panel, scope rules are editable without a redeploy, and SSH host keys are pinned.

  • Improvement
    Newer Claude and Codex models in the scan engine

    Support for newer models, sensitive data redacted before analysis, and steadier finding handling on long runs.

  • Fix
    Credits are refunded when a scan can’t run

    If the target is unreachable at preflight, or a run fails midway, the credits go back to your workspace.

  • Fix
    Schedules recover after maintenance

    Scheduled scans re-register if their job goes missing and resume right after a rolling deploy.

  • Fix
    Plus-addressed emails can register

    Sign-ups with addresses like name+team@company.com no longer fail when the access token is issued.

  • Fix
    Runner images build through mirror outages

    Image builds no longer fail when a Kali package mirror is down.