Combine source code, runtime application, and manual testing into one risk decision.
Eresus combines code, running application, API, identity, business logic, secret, and release-pipeline signals to turn application security testing from scanner output into a proof-driven program.
Vulnerabilities our researchers found and disclosed
Public advisories credited to the Eresus research team. The same people run your engagement.
This engagement creates value fastest for teams like these.
Security and engineering leadership
Teams that need exploit-backed proof before they reprioritize application, API, cloud, or identity work.
Product teams with customer-facing risk
Organizations shipping auth-heavy, multi-tenant, regulated, or internet-exposed systems where logic and authorization flaws matter.
Buyers who need proof, not alert volume
Programs that want reproducible findings, remediation direction, and a closure path instead of scanner noise.
Scope
Risk signals
Outcomes
Evidence standard
Proof you can inspect. Boundaries you can plan around.
Every engagement is bounded by written authorization, evidence handling, and a clear handoff. These are the defaults; the signed scope can tighten them.
Evidence you receive
- Written scope, authorization, and rules of engagement before testing starts.
- Reproducible evidence for each validated finding, with sensitive data redacted.
- Business impact, the affected boundary, and developer-ready remediation direction.
- Retest status for critical fixes; unresolved items remain visible.
Explicit exclusions
- Compliance certification or an audit opinion.
- Unscoped production denial-of-service, destructive actions, or data exfiltration.
- Full source review unless it is explicitly included in scope.
- A guarantee that no vulnerability remains after remediation.
Turn application security from a tool list into a decision system.
Problem
We identify which app, API, repository, and release flow carry material risk.
Attack scenario
We combine code signals, runtime surfaces, and business logic abuse in one attack path.
Proof
Findings are validated with exploit steps, HTTP requests, code traces, secret evidence, or CI output.
Delivery
Source code analysis, runtime testing, manual validation, and DevSecOps gates become one prioritized program.
The questions buyers want answered early.
How do you scope this engagement?+
What do we receive at the end?+
Do you help with remediation and retest?+
We tie risk to business impact.
Findings do not stop at severity labels. We explain which customer workflow, data class, or operational objective is affected.
Deliverables work for engineers and executives.
Engineering teams get reproducible proof and remediation direction; leadership gets the risk narrative, priority, and closure status.
Research and advisories that support this service motion.
Automated Vulnerability Scanning vs. Manual Penetration Testing: Which Do You Need?
When deciding on cybersecurity investments, IT teams and boards often have the same debate: 'Instead of spending thousands of dollars on manual p...
ERESUS-ADV-2026-002: Server-Side Request Forgery (SSRF) via Cloud Metadata Endpoints
Server-side request forgery in cloud-hosted URL fetch flows can expose metadata services, temporary IAM credentials, and internal configuration.
Critical Authentication Bypass via JWT Signature Verification Disabled in yargi-mcp
yargi-mcp decodes Clerk JWT tokens with signature verification disabled, enabling authentication bypass, forged identities, and arbitrary scope escalation.
Let’s scope this work against the surface that matters most.
Whether this starts as a pilot, a single application, a critical API, an AI agent flow, or a wider program, we start from the highest-impact surface.