CVE-2026-47826
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 · uneditedThe blobs.yml path key traversal vulnerability in the BOSH CLI tool allows an attacker to write arbitrary files and exfiltrate sensitive information. Affected versions: BOSH CLI tool versions prior to v7.10.4.
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 confidenceA path traversal vulnerability in the BOSH CLI tool's handling of blobs.yml configuration allows attackers to use specially crafted paths (e.g., ../../) to write files to arbitrary locations on the filesystem and read sensitive files, potentially leading to remote code execution or credential exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.10.4CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 BOSH CLI versionRun 'bosh --version' or 'bosh -v' to display the installed BOSH CLI version numberAffected if The version displayed is less than 7.10.4 (for example 7.10.3, 7.10.0, 7.9.x, etc.)
-
Locate blobs.yml configuration filesSearch for blobs.yml files in the environment using 'find . -name blobs.yml' or check the current working directory for a blobs.yml fileAffected if A blobs.yml file exists and is present in the BOSH deployment or release directory
-
Inspect blobs.yml for path traversal patternsExamine the contents of any found blobs.yml file and look for path entries containing '../' sequences or absolute paths pointing outside the expected blobstore directoryAffected if The blobs.yml contains path entries with ../ sequences or absolute paths pointing to sensitive system locations such as /etc/, ~/.ssh/, or other directories outside the intended blobstore
-
Verify BOSH blob management usageCheck if bosh commands related to blobs are used (bosh blob, bosh add blob, bosh sync blobs) in the environment or CI/CD pipelinesAffected if BOSH blob commands are actively used with the affected CLI version and a blobs.yml configuration file is present
A system is affected if the installed BOSH CLI version is below 7.10.4 AND a blobs.yml configuration file is being used, regardless of whether malicious path traversal entries are currently present in the configuration.
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 · scoped7.10.4
Upgrade BOSH CLI to version v7.10.4 or later to obtain the patch for this path traversal vulnerability.
BOSH CLI v7.10.4
- 1. Check current BOSH CLI version: bosh --version
- 2. If version is below 7.10.4, upgrade to version 7.10.4 or later using your package manager or: gem install bosh_cli -v 7.10.4
- 3. Verify the upgrade was successful: bosh --version
- 4. Confirm the installed version is 7.10.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47826 — 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-47826 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