CVE-2026-56279
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCapgo before 12.128.2 contains an information disclosure vulnerability in the get_orgs_v7(userid) RPC function that remains publicly invokable despite intended private access controls. Unauthenticated attackers can supply arbitrary user UUIDs to retrieve foreign users' organization membership, roles, management emails, and billing metadata.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCapgo before version 12.128.2 has an IDOR/broken access control vulnerability in the get_orgs_v7(userid) RPC function. The function, intended to be private, remains publicly accessible without authentication, allowing attackers to supply arbitrary user UUIDs and retrieve sensitive organizational data including membership, roles, management emails, and billing metadata.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo installation and versionCheck your installed Capgo version by running: capgo --version, or check the package.json/package-lock.json if using npm package, or check the Docker image tag if using containersAffected if Version is before 12.128.2
-
Confirm get_orgs_v7 function is exposedAttempt to access the get_orgs_v7 RPC endpoint directly without providing authentication credentials. This may be at an API endpoint like /api/v7/orgs or similar RPC endpoint depending on your Capgo deploymentAffected if The function returns organizational data without requiring any authentication token or login session
-
Test IDOR vulnerability with arbitrary user UUIDSend a request to the get_orgs_v7 function with a user UUID that differs from your authenticated identity (or no authentication), and observe if sensitive organizational data (membership, roles, emails, billing) is returnedAffected if You receive organizational data for a user different from your authenticated user, or receive data without any valid authentication
-
Verify authentication requirement on the endpointReview API gateway or application logs for unauthenticated requests to the get_orgs_v7 endpoint, or inspect the RPC function code/configuration to confirm if access controls are properly enforcedAffected if Requests without valid auth tokens are accepted and processed by get_orgs_v7
Your environment is affected if Capgo version is below 12.128.2 AND the get_orgs_v7 RPC function accepts requests without authentication and returns data for arbitrary user UUIDs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement proper authentication and authorization checks on the get_orgs_v7 function to ensure only the authenticated user can access their own organization data, and validate that the requested user UUID matches the caller's identity.
12.128.2 or later
- Upgrade Capgo to version 12.128.2 or later to remediate the missing authorization vulnerability in the get_orgs_v7(userid) RPC function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56279 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data