CVE-2026-56236
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 CLI before 12.128.2 contains arbitrary file overwrite vulnerabilities in login and build credentials operations that follow symlinks without validation. Attackers can create malicious symlinks in repositories to overwrite arbitrary files or expose credentials with world-readable permissions when developers run the CLI.
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 CLI versions before 12.128.2 fail to validate symlinks during login and build credentials operations. The CLI follows symlinks without checking if they point to unexpected locations, allowing attackers who can place malicious symlinks in repositories to overwrite arbitrary files on developer machines or create credential files with world-readable permissions.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/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.
-
Check Capgo CLI installed versionRun `capgo --version` or if installed via npm, run `npm list capgo` to see the installed versionAffected if Version is less than 12.128.2 (e.g., 12.128.1, 12.127.0, etc.)
-
Identify if login operation is usedReview your CI/CD pipelines, scripts, or manual workflows for use of `capgo login` commandAffected if You run `capgo login` in any repository or directory, especially those with untrusted contributors or content
-
Identify if build credentials operation is usedReview your workflows for use of `capgo build-credentials` or similar credential-related commandsAffected if You run credential-related Capgo CLI commands in repositories that may contain symlinks you did not create
-
Check for symlinks in your working directoryRun `find . -type l -ls` to list all symbolic links in the current directory and subdirectoriesAffected if Symlinks exist that point to sensitive paths like home directory, .capgo folder, or credential storage locations
-
Verify credential file permissionsCheck permissions on `~/.capgo/` directory and any credential files: `ls -la ~/.capgo/` and `ls -la ~/.capgo/*.json 2>/dev/null`Affected if Any credential files exist with permissions allowing world or group read access (e.g., 644, 664, or worse)
You are affected if you are running Capgo CLI version below 12.128.2 AND you use login or build credentials operations in directories that may contain untrusted symlinks.
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.
From vendor dataUpgrade Capgo CLI to version 12.128.2 or later which includes symlink validation. Until upgraded, avoid running Capgo CLI in repositories with untrusted content or untrusted contributors.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56236 — 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-56236 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