CVE-2026-56282
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 unauthenticated /replication endpoint that exposes internal PostgreSQL replication telemetry including slot names and WAL LSN positions. Attackers can access this endpoint without authentication to retrieve sensitive infrastructure details such as replication slot names, confirmed_flush_lsn, restart_lsn values, and database error messages for reconnaissance purposes.
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 unauthenticated /replication endpoint that exposes internal PostgreSQL replication telemetry including replication slot names, WAL LSN positions (confirmed_flush_lsn, restart_lsn), and database error messages. Attackers can use this information for reconnaissance to map internal database infrastructure.
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 (e.g., check installed packages, docker containers, or the application binary) and determine its version using the package manager, container labels, or version file.Affected if The installed version is earlier than 12.128.2
-
Confirm the /replication endpoint existsSend an HTTP GET request to the /replication endpoint of the Capgo application (e.g., curl http://<capgo-host>/replication or https://<capgo-host>/replication).Affected if The endpoint responds with HTTP 200 or any status without requiring authentication credentials.
-
Inspect response for replication telemetryExamine the HTTP response body from the /replication endpoint for PostgreSQL-specific data such as replication slot names, confirmed_flush_lsn, restart_lsn, or database error messages.Affected if The response contains replication slot names, WAL LSN positions (confirmed_flush_lsn, restart_lsn), or internal database error messages.
A user is affected if the Capgo version is earlier than 12.128.2 AND the /replication endpoint is accessible without authentication AND returns PostgreSQL replication telemetry.
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 authentication on the /replication endpoint or upgrade Capgo to version 12.128.2 or later to remediate this information disclosure vulnerability.
12.128.2 or later
- Upgrade Capgo to version 12.128.2 or later to remediate the unauthenticated information disclosure vulnerability
- After upgrading, verify that the /replication endpoint now requires authentication or is properly restricted
- Review access logs to confirm no unauthorized access to replication telemetry occurred prior to the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56282 — 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-56282 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