Skip to content

← Actionable
High, CVSS 7.1amended

Convoy: Cross-Tenant Source IDOR Leaks Plaintext Message Broker Credentials

CVE-2026-81505GHSA-p5vg-v7mj-f6q4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/frain-dev/convoy 0.9.3-0.20260724092134-1cc67cd16fb1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-81505: 0.46% estimated exploitation activity in the next 30 days; percentile 40.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-p5vg-v7mj-f6q4

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6523

  4. Revision 1 · created ·

    Published from osv record GHSA-p5vg-v7mj-f6q4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-81505

Advisory: Convoy: Cross-Tenant Source IDOR Leaks Plaintext Message Broker Credentials
IDs: CVE-2026-81505, GHSA-p5vg-v7mj-f6q4
Record: https://patchnext.com/advisories/cve-2026-81505 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/frain-dev/convoy 0.9.3-0.20260724092134-1cc67cd16fb1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/frain-dev/convoy: affected < 0.9.3-0.20260724092134-1cc67cd16fb1; fixed in 0.9.3-0.20260724092134-1cc67cd16fb1

## Suggested inspection (read-only)
- Go github.com/frain-dev/convoy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/frain-dev/convoy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p5vg-v7mj-f6q4 (OSV record GHSA-p5vg-v7mj-f6q4 lists affected ranges: Go github.com/frain-dev/convoy >=0 <0.9.3-0.20260724092134-1cc67cd16fb1 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6523 (OSV record GO-2026-6523 lists affected ranges: Go github.com/frain-dev/convoy >=0 <0.9.3-0.20260724092134-1cc67cd16fb1 (fixed))
- Verified: https://github.com/advisories/GHSA-p5vg-v7mj-f6q4 (GitHub-reviewed advisory GHSA-p5vg-v7mj-f6q4 lists affected ranges: Go github.com/frain-dev/convoy >=0 <0.9.3-0.20260724092134-1cc67cd16fb1)

Commands are suggestions: review each one before running it.

Loading voting…