Skip to content
Automated Vulnerability Remediation

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

What it fixes itself
Pull requestConfiguration changePull request (application and infrastructure code), configuration change
Who approves
Developer reviews each generated fix before merge
Resolves the owner
Yes: routes to the team that owns the code
Scanners it reads
Wiz, Tenable, Upwind, Qualys, Snyk
Price
None found on 10 Nov 2026

Averlon: 40 fact lines read

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

What it is

Agentic remediation (exposure/attack-chain analysis with fixes delivered into developer workflows).

What it does well

Averlon pairs per-environment applicability, reachability and attack-chain analysis with a GitHub Actions remediation flow that opens ready-to-merge pull requests and assigns a ticket to the code owner, with a published customer result of 3,400 tickets reduced to 260 pull requests.

Where it is limited

Averlon's customer example leaves the customer unnamed and the method unstated; none found on 10 Nov 2026: a new-CVE time-to-answer, a customer agent builder, named ticketing integrations, or pricing.

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. Averlon has 40 lines on file, read up to 10 Nov 2026; the Averlon pages behind them are listed under Sources.

Proves exploitability in your environment

  • Vendor's claim: Averlon says it checks applicability against the customer's own environment and tests reachability across network configuration, IAM policies and Kubernetes RBAC. (source, read 10 Nov 2026)
  • Vendor's claim: Attack chains are mapped to MITRE ATT&CK, with blast radius, and fixes that break the most chains are placed first. (source, read 10 Nov 2026)
  • Vendor's claim: The homepage demo shows per-finding evidence fields (network exploitability, external exposure, known exploits, access to critical data, attack-chain membership) behind each triage decision. (source, read 10 Nov 2026)
  • Vendor's claim: Averlon lists compensating-control assessment as a capability, to find controls already limiting risk. (source, read 10 Nov 2026)

Ships the fix

  • Vendor's claim: Averlon says it delivers context-aware fixes inside IDEs, source control and CLI, and applies the same reasoning before merge. (source, read 10 Nov 2026)
  • Vendor's claim: Its GitHub Actions generate ready-to-merge pull requests for application and infrastructure issues. (source, read 10 Nov 2026)
  • Vendor's claim: Fix actions cover container images, Terraform and Pulumi IaC, and Kubernetes Helm charts. (source, read 10 Nov 2026)
  • Vendor's claim: The vendor's example flow expects a human developer to review each generated fix (about 15 minutes per fix in its example). (source, read 10 Nov 2026)
  • Vendor's claim: Where patching is not the route, Averlon lists risk mitigation by adjusting compensating controls or applying tailored remediation. (source, read 10 Nov 2026)
  • Vendor's claim: Precog evaluates proposed changes in CI (for example GitHub) and delivers the fix to the developer alongside the alert. (source, read 10 Nov 2026)

Finds the owner

  • Vendor's claim: Averlon traces a base-image vulnerability to the Dockerfile and routes it to the team that owns it. (source, read 10 Nov 2026)
  • Vendor's claim: For each fix group it creates a pull request plus a ticket for that PR assigned to the developer who owns the code. (source, read 10 Nov 2026)
  • Vendor's claim: In the vendor's customer example, issues were mapped to their source (base image or dependency) and grouped, instead of being assigned individually. (source, read 10 Nov 2026)

Speed on a new disclosure

  • Vendor's claim: A customer quote on the vendor site credits Averlon with saving time in 0-day incident response for the libWebp vulnerability. (source, read 10 Nov 2026)
  • Vendor's claim: Averlon published a response write-up dated Nov 2, 2026 on CVE-2026-98432, about 18 days after the CVE was published on October 15, 2026, covering which network paths expose a host. (source, read 10 Nov 2026)
  • Vendor's claim: It also published an explainer for React2Shell (CVE-2025-55182) on Dec 4, 2025, updated as new CVEs followed. (source, read 10 Nov 2026)
  • Vendor's claim: Averlon runs a vulnerability intelligence site (research.averlon.ai); its page content was not readable in a plain fetch beyond the title. (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: A stated time-to-answer for a new CVE (minutes or hours figure) on home, platform or why-averlon pages (source, read 10 Nov 2026)

Agents you can shape

  • Vendor's claim: The platform lists Mitigation Agents and Remediation Agents as ready-made components. (source, read 10 Nov 2026)
  • Vendor's claim: The homepage demo shows a 'Remediation Agent' proposing a pull request that waits for merge, and 'Autonomous AI Triage' on each finding. (source, read 10 Nov 2026)
  • Vendor's claim: Guardrail described: fixes arrive as pull requests that pass checks and are reviewed by developers before merge. (source, read 10 Nov 2026)
  • Vendor's claim: Averlon also runs Cynos, a separate inference platform giving API access to models from several providers (not described as a customer agent builder). (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: An agent builder or customer-built agent feature on averlon.ai platform pages (source, read 10 Nov 2026)

Works on the stack you have

  • Vendor's claim: Averlon integrates with scanners including Wiz, Tenable, Upwind, Qualys and Snyk. (source, read 10 Nov 2026)
  • Vendor's claim: It ingests findings from posture, identity, runtime, vulnerability scanners and code. (source, read 10 Nov 2026)
  • Vendor's claim: A Wiz integration post describes Wiz supplying risk context while Averlon does triage and remediation. (source, read 10 Nov 2026)
  • Vendor's claim: Remediation actions are published on the GitHub Marketplace; Terraform, Pulumi and Helm are read. (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: Named ticketing integrations (Jira, ServiceNow); the blog says tickets are auto-assigned but does not name the system (source, read 10 Nov 2026)

Proof

  • Vendor's claim: A vendor-published customer example: 110,000 critical and high issues, 3,400 tickets, became 260 pull requests; MTTR fell from 45 days to 6 days (customer unnamed). (source, read 10 Nov 2026)
  • Vendor's claim: The same example reports mean time to remediate down from 45 days to 6 days. (source, read 10 Nov 2026)
  • Vendor's claim: The Why Averlon page shows a noise-reduction example (140K issues on 28K assets reduced to 6,924 critical issues on 310 assets); customer unnamed, method not stated on the page. (source, read 10 Nov 2026)
  • Vendor's claim: Homepage headline metrics (90% faster remediation, 95% fewer false positives) are stated without a method on the page. (source, read 10 Nov 2026)
  • Vendor's claim: Named CISO testimonials appear (for example Scott Roberts, CISO) but company names are mostly withheld. (source, read 10 Nov 2026)
  • Vendor's claim: Published research content includes a whitepaper on development-environment attacks (Oct 2025 to Apr 2026). (source, read 10 Nov 2026)

Profile facts

  • Vendor's claim: Averlon came out of stealth May 23, 2024 with $8M led by Voyager Capital (Salesforce Ventures, Outpost Ventures), for $10.5M total funding. (source, read 10 Nov 2026)
  • Vendor's claim: The investment was led by Voyager Capital with Salesforce Ventures and Outpost Ventures. (source, read 10 Nov 2026)
  • Vendor's claim: Founded in 2022 by Sunil Gottumukkala (CEO) and Vishal Agarwal (CTO). (source, read 10 Nov 2026)
  • Vendor's claim: Product names: Averlon Agentic Remediation Operations platform, Precog (pre-merge), Cynos (inference platform). (source, read 10 Nov 2026)
  • Vendor's claim: Platform spans VM, CSPM, KSPM, CIEM, CWPP, ASPM and DSPM capability labels. (source, read 10 Nov 2026)
  • None found on 10 Nov 2026: Pricing, headcount, HQ and customer count on home, about, platform, why-averlon (source, read 10 Nov 2026)

Sources

10 sources, each with its read date
  1. Averlon: www.averlon.ai/platform, read 10 Nov 2026
  2. Averlon: www.averlon.ai/, read 10 Nov 2026
  3. Averlon: www.averlon.ai/why-averlon, read 10 Nov 2026
  4. Averlon: www.averlon.ai/blog/automating-remediation-application-infrastructure-security-i, read 10 Nov 2026
  5. Averlon: www.averlon.ai/blog/cve-2026-98432-linux-kernel-tcp-use-after-free, read 10 Nov 2026
  6. Averlon: www.averlon.ai/blog/react2shell-cve-2025-55182-explained, read 10 Nov 2026
  7. Averlon: research.averlon.ai/vulnerability-intelligence, read 10 Nov 2026
  8. Averlon: www.averlon.ai/blog/averlon-and-wiz-accelerate-remediation-and-reduce-exposure, read 10 Nov 2026
  9. Averlon: www.averlon.ai/blog/averlon-comes-out-of-stealth-mode-with-10m-in-funding-to-adv, read 10 Nov 2026
  10. Averlon: www.averlon.ai/about, read 10 Nov 2026

Last reviewed 10 Nov 2026.