CVE-2026-56318
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 /private/validate_password_compliance endpoint that returns different error responses for malformed, non-existent, and existing organization IDs. Unauthenticated attackers can enumerate valid organization UUIDs by observing response status codes and error messages, allowing confirmation of organization existence.
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 12.128.2 has an information disclosure vulnerability in the /private/validate_password_compliance endpoint. Unauthenticated attackers can distinguish between malformed, non-existent, and existing organization UUIDs by observing different HTTP status codes and error messages in responses, enabling organization ID enumeration.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 versionLocate the Capgo installation and determine its version number by checking package.json, a config file, or the application's version endpoint if availableAffected if The installed version is before 12.128.2
-
Verify the vulnerable endpoint existsCheck if the /private/validate_password_compliance endpoint is accessible by making a request to it (e.g., curl https://your-capgo-host/private/validate_password_compliance)Affected if The endpoint responds with any HTTP status code (even an error) indicating it exists and is reachable
-
Test for inconsistent error responsesSend requests to the endpoint with three types of organization UUIDs: a malformed UUID (e.g., 'not-a-uuid'), a valid-format UUID that does not exist (e.g., '00000000-0000-0000-0000-000000000000'), and a known-valid organization UUID. Compare the HTTP status codes and error messages for eachAffected if Different status codes (e.g., 400 vs 404 vs 200) or different error messages are returned for these three cases, enabling UUID enumeration
If Capgo is installed with a version before 12.128.2 and the /private/validate_password_compliance endpoint returns different status codes or messages for malformed, non-existent, and existing organization UUIDs, the environment is affected by this vulnerability.
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 · scopedNormalize error responses to return identical status codes and messages regardless of whether the organization ID is malformed, non-existent, or valid, preventing enumeration of valid organization UUIDs.
12.128.2
- 1. Identify the current installed version of Capgo
- 2. Upgrade Capgo to version 12.128.2 or later
- 3. Verify the upgrade was successful by checking the new version number
- 4. Test that the /private/validate_password_compliance endpoint now returns consistent responses for all organization ID variations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56318 — 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-56318 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