Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-81505

Vulnerability in github.com/frain-dev/convoy (CVE-2026-81505)

Summary

Vulnerability in github.com/frain-dev/convoy (CVE-2026-81505). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/projects/{projectID}/sources/{sourceID}. Mitigation: upgrade to 0.9.3-0.20260724092134-1cc67cd16fb1 or later.

Original description

The description as published by the source.

Summary

frain-dev/convoy (all versions up to and including v26.6.2, no patch
available) lets any authenticated caller who is authorized on at least one
project read ANY OTHER project's "Source" record by ID via
GET /api/v1/projects/{projectID}/sources/{sourceID} -- regardless of whether
that Source actually belongs to the project named in the URL. The response
includes the Source's full PubSub broker configuration in plaintext
(AMQP/Kafka/SQS/Google credentials), with no redaction.

Details

Handler.GetSource (api/handlers/source.go) resolves the caller's
authorization against the {projectID} in the URL via retrieveProject(), then
calls sources.Service.FindSourceByID(ctx, project.UID, sourceID)
(internal/sources/impl.go). That function accepts a projectID parameter but
never uses it:

func (s *Service) FindSourceByID(ctx context.Context, projectID, id string) (*datastore.Source, error) {
    row, err := s.repo.FetchSourceByID(ctx, common.StringToPgText(id))
    ...
}

The underlying SQL query (internal/sources/repo/queries.sql,
fetchSourceByID) has no project_id predicate at all:

SELECT ... FROM convoy.sources AS s
LEFT JOIN convoy.source_verifiers sv ON s.source_verifier_id = sv.id
WHERE s.id = $1 AND s.deleted_at IS NULL

So the {projectID} in the URL only gates "is the caller authorized to view
a project" -- it never re-validates that the fetched Source actually
belongs to that project. LoadSourcesPaged (the list endpoint) does
c…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-81505 has been found in github.com/frain-dev/convoy.
Attackers can target a specific entry point like GET /api/v1/projects/{projectID}/sources/{sourceID} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/frain-dev/convoy to 0.9.3-0.20260724092134-1cc67cd16fb1 or later.
If unsure, ask your IT team or search "github.com/frain-dev/convoy CVE-2026-81505" on the vendor's site.

CVE-2026-81505 (github.com/frain-dev/convoy) — CWE-639
Attack surface: GET /api/v1/projects/{projectID}/sources/{sourceID} / GET /api/v1/projects/{attacker_project_id}/sources/{victim_source_id} / Handler.GetSource / fetchSourceByID
Patched: 0.9.3-0.20260724092134-1cc67cd16fb1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in github.com/frain-dev/convoy. Attackers reach the vulnerable code path via GET /api/v1/projects/{projectID}/sources/{sourceID}.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/frain-dev/convoy. Attack surface: GET /api/v1/projects/{projectID}/sources/{sourceID} / GET /api/v1/projects/{attacker_project_id}/sources/{victim_source_id} / Handler.GetSource / fetchSourceByID.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.9.3-0.20260724092134-1cc67cd16fb1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/v1/projects/{projectID}/sources/{sourceID} requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/frain-dev/convoy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/frain-dev/convoy' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/frain-dev/convoy を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/v1/projects/{projectID}/sources/{sourceID}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/projects/{projectID}/sources/{sourceID} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/frain-dev/convoy to 0.9.3-0.20260724092134-1cc67cd16fb1

    ステージング環境で 0.9.3-0.20260724092134-1cc67cd16fb1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/v1/projects/{projectID}/sources/{sourceID} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/frain-dev/convoy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.3-0.20260724092134-1cc67cd16fb1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details