Backed by Y Combinator From the #1 US hacking team

Leave nothing to chance.

Veria is an autonomous pentester: it maps your entire attack surface, proves real exploits, and drafts the fix.

Get a demo Read our research

You're in good company. These teams already use Veria.

From findings to merged fix. Veria handles all of it.

Feed

Open 4 In Progress 2 Fixed 38 False Positive Won't Fix

All repositories Status Open Search findings…

Finding Location Status Assignees Detected

critical VERIA-231 SQL injection in invoice export The org filter is interpolated into a raw SQL query. acme/api-gateway main Open JD 2 hours ago

critical VERIA-230 Forged payment webhooks mark invoices as paid A leaked webhook signing secret lets any user forge payments. acme/api-gateway main Open — 5 hours ago

high VERIA-233 Viewers can invite workspace admins acme/web main Open — 1 hour ago

high VERIA-229 Password reset token never expires Reset tokens still work after they're used. acme/auth main Open MK 9 hours ago

Everything in one feed

All your findings in one list, sorted by severity. Open one to see the vulnerable code and the fix.

#security-alerts

Veria AI APP 2:31 PM

In Progress·Critical

VERIA-231: SQL injection in invoice export

src/invoices/export.ts:41-43 ↗

acme/api-gateway

View Details Change Status

JD 2 replies Last reply today at 2:44 PM

In Progress 1

! ACM-412 [VERIA-231] SQL injection in invoice export JD

Backlog 2

! ACM-411 [VERIA-230] Forged payment webhooks mark invoices as paid

ACM-409 [VERIA-227] Rate limit bypass via header spoofing

In your workflow

New findings post to Slack and become Linear issues. Update the status in one place and it changes in both.

Dependencies

Veria matches your dependencies against known advisories. Then it checks whether your code calls the vulnerable part.

fix: parameterize invoice export query #1288

Open veria-ai wants to merge 1 commit into main from veria/fix-veria-231

veria-ai bot opened this pull request

Fixes VERIA-231: SQL injection in invoice export.

filter is now passed to db.query as a bound parameter instead of being interpolated into the SQL string.

All checks have passed 6 successful checks

Automatic fixes

Veria writes the patch and opens the pull request. Your team reviews and merges it like any other change.

Real reviews from open‑source customers.

Merged feat(devex): distributed owners.yaml ownership with a single resolver #68872

‎.github/scripts/assign-reviewers.js‎

58 + const launcher =

+        "import sys, runpy; sys.path.insert(0, 'tools/owners'); runpy.run_module('posthog_owners', run_name='__main__')"

60 + const result = spawnSync(python, ['-c', launcher], {

veria-ai bot Jul 15 View on GitHub ↗

High: Repository-root module shadowing

The python -c invocation retains the current repository directory on sys.path immediately after tools/owners. An attacker can land an unprotected root-level yaml.py or yaml/__init__.py, then have it imported instead of PyYAML by a future pull_request_target run and read the app token from GITHUB_TOKEN. Run Python in isolated mode so the working directory and environment-provided import paths are excluded.

Suggested change

60 - const result = spawnSync(python, ['-c', launcher], {

60 + const result = spawnSync(python, ['-I', '-c', launcher], {

Merged feat: add Infisical OAuth 2.0 support #6772

‎backend/src/server/plugins/auth/verify-auth.ts‎

25 + // lists only AuthMode.OAUTH is NOT satisfied by a session JWT. To fence a sensitive route off

26 + // from delegated access, omit AuthMode.JWT or check req.auth.oauthClientId in the handler.

27 + if (strategy === AuthMode.JWT && req.auth.authMode === AuthMode.OAUTH) return true;

veria-ai bot Jun 9 View on GitHub ↗

High: OAuth tokens bypass scopes on JWT-only account routes

AuthMode.OAUTH is accepted anywhere a route lists AuthMode.JWT, but OAuth scopes are only enforced when handlers later build org/project permissions. A delegated token with empty or unrelated scopes can still call JWT-only user routes such as GET /api/v1/user/me/totp to read TOTP recovery codes, DELETE /api/v1/user/me/totp to remove MFA, or session revocation endpoints because those handlers trust authentication alone.

Require routes to explicitly opt in to delegated OAuth access, or add a central scope check before allowing AuthMode.OAUTH through JWT routes.

Suggested change

27 - if (strategy === AuthMode.JWT && req.auth.authMode === AuthMode.OAUTH) return true;

27 + if (strategy === AuthMode.JWT && req.auth.authMode === AuthMode.OAUTH) return false;

Merged feat(mcp/ui): expose true_passthrough and oauth_delegate auth types with a no-auth warning #32414

‎litellm/proxy/_experimental/mcp_server/server.py‎

123 + if not parts.hostname:

124 + return None

125 + netloc = f"{parts.hostname}:{parts.port}" if parts.port else parts.hostname

126 + return urlunsplit((parts.scheme, netloc, parts.path, "", "")) or None

veria-ai bot Jul 9 View on GitHub ↗

High: Path credentials are written to spend logs

MCP URLs can carry credentials in the path, including formats such as /mcp/<token>. Because this value is persisted in mcp_tool_call_metadata, a user can invoke an allowed tool, read the resulting request log, and recover the upstream credential. Log only the origin unless there is a credential-aware path sanitizer.

Suggested change

126 - return urlunsplit((parts.scheme, netloc, parts.path, "", "")) or None

126 + return urlunsplit((parts.scheme, netloc, "", "", "")) or None

Security review on every PR

Veria reviews every pull request as it opens. If a change adds a vulnerability, it comments on that line with a fix.

Catch vulnerabilities before they matter. See what Veria finds.

Get a demo