CVE-2026-47830: Windows BOSH Stemcell Builder Privilege Escalation Vulnerability
A permissions flaw in BOSH Windows stemcell builder allows authenticated users with limited privileges to replace critical system executables (the BOSH agent service wrapper or the BOSH agent itself) with malicious versions. When the affected service restarts or the system reboots, these replaced files execute with full system privileges (NT AUTHORITY\SYSTEM), giving an attacker complete control of the host. This is a local privilege escalation vulnerability that affects BOSH-Windows-stemcell-builder versions before v2019.98.
Source data · NVD / CISA · public domain
- CVSS
- 3.0 · 8.8 HIGH · CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Weaknesses (CWE)
- —
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-09 / 2026-07-09
NVD description (verbatim)
Incorrect 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.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-47830 stems from incorrect permission assignment in the BOSH.Utils.psm1 PowerShell module used by bosh-windows-stemcell-builder. The vulnerability allows low-privilege authenticated users to write to or overwrite files in the C:\bosh directory, specifically targeting service_wrapper.exe and bosh-agent.exe. Because these executables are subsequently invoked by the Windows service control manager (typically running as NT AUTHORITY\SYSTEM), an attacker can inject arbitrary code that executes with full system privileges upon service restart or system reboot. The flaw is a classic case of insecure file permissions enabling privilege escalation.
Business impact
Organizations using BOSH for Windows infrastructure automation face a critical insider threat. Any authenticated user (developer, operator, or contractor with system access) can escalate privileges and compromise host integrity. This enables data exfiltration, lateral movement within the BOSH-managed environment, installation of persistent backdoors, denial of service, and tampering with cloud infrastructure deployments. For enterprises relying on BOSH for multi-tenant or production cloud environments, this represents a path to complete infrastructure compromise.
Affected systems
The vulnerability affects bosh-windows-stemcell-builder versions prior to v2019.98. Any Windows-based BOSH deployment using a vulnerable stemcell version is at risk. Organizations should inventory their BOSH Windows stemcell versions in development, staging, and production environments to determine exposure.
Exploitability
The attack requires local access and valid credentials but no special privileges—a low-privilege authenticated user can exploit this. No user interaction or complex conditions are needed; an attacker simply overwrites the target executables and triggers a service restart or system reboot. The CVSS 3.0 score of 8.8 (HIGH) reflects the ease of exploitation and the severe impact (full system compromise). This vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog as of the published date, but the straightforward exploitation path means attack tooling could emerge quickly.
Remediation
Upgrade bosh-windows-stemcell-builder to version v2019.98 or later. This patched version corrects the file permission assignment in BOSH.Utils.psm1 to restrict write access to the C:\bosh directory to authorized service accounts only. After upgrading the builder, rebuild and redeploy Windows stemcells to all BOSH environments.
Patch guidance
1. Verify your current bosh-windows-stemcell-builder version via your BOSH director or stemcell metadata. 2. Obtain version v2019.98 or later from the official BOSH project repository. 3. Update your stemcell build pipeline to use the patched version. 4. Rebuild all Windows stemcells in your environment. 5. Redeploy affected Windows VMs to apply the corrected permissions. 6. Test service restart and system reboot scenarios in a non-production environment first to ensure service stability. 7. For existing deployments running vulnerable stemcells, consider implementing operating system-level access controls and audit logging to detect unauthorized file modifications in C:\bosh until stemcells can be updated.
Detection guidance
Monitor Windows event logs for: - Unauthorized modifications to C:\bosh\service_wrapper.exe or C:\bosh\bosh-agent.exe (File Integrity Monitoring or Windows Auditing). - Unexpected SYSTEM-level process launches from the C:\bosh directory. - Failed or unusual service restarts for the BOSH agent service. Implement file integrity checks on critical BOSH binaries and alert on any changes outside of scheduled maintenance. Use Windows Auditing to log and monitor object access (Create, Write) to the C:\bosh directory, filtering for non-service accounts.
Why prioritize this
This vulnerability merits urgent patching. It combines a low attack barrier (any authenticated user) with maximum impact (full system compromise). BOSH environments often run cloud infrastructure that may host customer workloads or sensitive internal applications. The attacker does not need special tools or exploits; standard file operations suffice. Although not yet appearing in active threat intelligence, the simplicity of exploitation and the high-stakes environment make this a near-term priority, especially for production or multi-tenant BOSH deployments.
Risk score, explained
The CVSS 3.0 score of 8.8 reflects: Attack Vector (Local) and low Attack Complexity, combined with low Privilege Requirements. The impact scores are all High—full confidentiality, integrity, and availability compromise of the affected system. The Scope is Changed because privilege escalation on one system can be used to compromise other systems in the BOSH-managed infrastructure. No mitigating factors (such as user interaction or attack complexity) reduce the score.
Frequently asked questions
Do I need to patch if I only use BOSH for Linux deployments?
No. This vulnerability is specific to bosh-windows-stemcell-builder and affects Windows-based BOSH deployments only. Linux stemcells and deployments are not impacted.
Can this vulnerability be exploited remotely?
No. The attack requires local authentication and file system access to C:\bosh. It cannot be exploited over the network without first gaining authenticated local access to the Windows host.
What happens if I cannot patch immediately?
Implement strict access controls on the C:\bosh directory, restricting write permissions to only the BOSH agent service account and administrators. Enable Windows Auditing and file integrity monitoring on service_wrapper.exe and bosh-agent.exe. Limit which users can authenticate locally to BOSH-managed Windows systems. Monitor for any unauthorized file modifications and service restarts.
How do I confirm if my stemcells are vulnerable?
Check the version of bosh-windows-stemcell-builder used to build your current stemcells. Versions prior to v2019.98 are vulnerable. You can verify the stemcell version via the BOSH director metadata or release notes associated with your deployment manifests.
This analysis is based on publicly available vulnerability data and vendor advisories current as of the publication date. Security researchers should verify all patch versions, affected product ranges, and remediation steps against the official BOSH project repository and vendor documentation before deploying fixes in production. This vulnerability intelligence is provided for informational purposes and does not constitute legal or compliance advice. Organizations must assess their specific infrastructure and threat landscape to determine appropriate remediation timelines. No exploit code or weaponized proof-of-concept details are provided or endorsed. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2016-20062HIGHSQL Injection in Simply Poll 1.4.1 WordPress Plugin - Unauthenticated Data Theft
- CVE-2016-20063HIGHSQL Injection in Single Personal Message 1.0.3 – Credential & Data Theft Risk
- CVE-2016-20065HIGHUnauthenticated SQL Injection in Product Catalog 8 WordPress Plugin
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20068HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20069HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20071HIGHCritical SQL Injection in WordPress 404 Redirection Manager Plugin v1.0
- CVE-2016-20072HIGHBBS e-Franchise WordPress Plugin SQL Injection – Remote Data Exfiltration Risk