CVE-2026-47830
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 · uneditedIncorrect Permission Assignment in BOSH.Utils.psm1 in BOSH-Ecosystem bosh-windows-stemcell-builder allows low-privilege authenticated users to overwrite C:\bosh\service_wrapper.exe or C:\bosh\bosh-agent.exe and gain NT AUTHORITY\SYSTEM on the next service restart or reboot. This can lead to full host control. Affected versions: bosh-windows-stemcell-builder versions prior to v2019.98.
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 confidenceIncorrect permission assignment in BOSH.Utils.psm1 allows low-privilege authenticated users to overwrite C:\bosh\service_wrapper.exe or C:\bosh\bosh-agent.exe. These executables run as NT AUTHORITY\SYSTEM when the bosh-agent service restarts or the host reboots, enabling arbitrary code execution with SYSTEM privileges and full host compromise.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 if BOSH directory and vulnerable executables existVerify that the C:\bosh\ directory exists and contains service_wrapper.exe or bosh-agent.exeAffected if The directory C:\bosh\ exists and contains service_wrapper.exe or bosh-agent.exe files - the environment uses BOSH for Windows deployment and may be affected
-
Inspect file permissions on service executablesRight-click on service_wrapper.exe and bosh-agent.exe in C:\bosh\, select Properties > Security, and examine which users or groups have Write or Modify permissionsAffected if Authenticated users or low-privilege accounts have Write or Modify permissions on these executable files
-
Check parent directory permissionsRight-click on C:\bosh\ folder, select Properties > Security, and verify which users or groups have Write or Modify permissions on the directoryAffected if Authenticated users or low-privilege accounts have Write or Modify permissions on the C:\bosh\ directory itself
-
Verify BOSH.Utils.psm1 module location and versionLocate BOSH.Utils.psm1 in the BOSH installation (typically in the PowerShell modules path or alongside BOSH binaries) and check the file version or modification date if availableAffected if BOSH.Utils.psm1 exists and its version predates the v2019.98 patch, indicating it may have the permission vulnerability
-
Test write access with low-privilege accountUsing a standard user account (non-admin), attempt to create or modify a test file in C:\bosh\ or copy a file over service_wrapper.exe/bosh-agent.exeAffected if A low-privilege authenticated user can successfully write or modify files in the C:\bosh\ directory or overwrite the service executables
The environment is affected if C:\bosh\ contains service_wrapper.exe or bosh-agent.exe AND low-privilege authenticated users have Write or Modify permissions on these executables or their parent directory.
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 · scopedRestrict file permissions on C:\bosh\service_wrapper.exe and C:\bosh\bosh-agent.exe to prevent write access by non-privileged users, or upgrade bosh-windows-stemcell-builder to v2019.98 or later which contains the corrected permissions.
bosh-windows-stemcell-builder v2019.98 or later
- 1. Identify the current version of bosh-windows-stemcell-builder installed in your environment
- 2. Download bosh-windows-stemcell-builder v2019.98 or later from the official Cloud Foundry BOSH-Ecosystem repository
- 3. Replace the existing bosh-windows-stemcell-builder installation with the new version
- 4. Verify that BOSH.Utils.psm1 has been updated and the file permissions are correctly configured
- 5. Ensure that C:\bosh\service_wrapper.exe and C:\bosh\bosh-agent.exe have appropriate access controls to prevent unprivileged modification
- 6. Test the deployment to confirm the service starts correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47830 — 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-47830 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