CVE-2026-56302
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 unsecured images bucket lacking any row level security controls, allowing unauthenticated attackers to read, insert, and delete stored app icons. Remote attackers can exploit this misconfiguration to delete all icons and leak sensitive app IDs and user IDs.
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 unsecured cloud storage bucket for app icons that lacks both authentication requirements and row-level security controls. Unauthenticated remote attackers can read, insert, and delete icon files, enabling them to delete all stored icons and exfiltrate sensitive app IDs and user IDs embedded in the stored data.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Verify Capgo installation versionRun the command to check the installed Capgo version (e.g., capgo --version, or check package.json, or query the Capgo API endpoint for version info) and compare it against the affected range: versions before 12.128.2 are vulnerableAffected if The installed version is below 12.128.2
-
Inspect storage bucket accessibilityExamine the cloud storage bucket configuration used by Capgo for app icons. Attempt an unauthenticated HTTP request to the bucket endpoint or review the bucket policy/ACL settings to determine if public access is allowedAffected if The bucket permits unauthenticated (anonymous) read, write, or delete operations without requiring credentials
-
Confirm row-level security configurationReview the storage bucket settings or database policies to determine whether row-level security (RLS) or equivalent access control policies are enforced on the icon storageAffected if Row-level security controls are disabled or not configured for the icon storage
-
Verify IAM policy restrictionsInspect the Identity and Access Management (IAM) policies attached to the storage bucket or the service account used by Capgo to determine if least-privilege principles are appliedAffected if The IAM policies allow broad CRUD operations (read, write, delete) to the bucket without restrictive conditions or principal limitations
A Capgo installation is affected if it runs a version below 12.128.2 AND the associated cloud storage bucket for app icons is publicly accessible without authentication or lacks row-level security and restrictive IAM policies.
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 · scopedEnable authentication on the storage bucket, implement row-level security policies to restrict access to authorized users only, and configure least-privilege IAM policies to prevent unauthorized CRUD operations.
Capgo version 12.128.2 or later
- 1. Identify the Capgo installation in your environment
- 2. Check the current installed version of Capgo
- 3. If the version is before 12.128.2, upgrade to version 12.128.2 or later
- 4. After upgrading, verify that the images bucket now has proper row-level security controls enabled
- 5. Confirm that unauthenticated access to the images bucket is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56302 — 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-56302 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