During bosh create-env and bosh delete-env, the CLI uploads compiled CPI packages and rendered job templates to the new VM's DAV blobstore over HTTPS without verifying the server certificate, even though a CA certificate for that endpoint is available in the installation manifest. A network attacker can terminate the TLS connection, harvest the Basic-auth credentials, and read the rendered-templates archive containing every bootstrap secret for the new BOSH Director, then replay the credentials against the real VM's agent for root code execution. Affected versions: bosh-cli versions prior to v7.10.4.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-47828 affects BOSH CLI operations during create-env and delete-env workflows, where compiled CPI packages and rendered job templates are uploaded to a DAV blobstore over HTTPS without server certificate validation. Despite having a valid CA certificate available in the installation manifest, the CLI fails to verify the endpoint's identity, creating a critical window for network attackers. This vulnerability is particularly dangerous because it exposes bootstrap credentials and rendered templates containing every secret needed to configure a new BOSH Director—secrets that persist in memory and files throughout the deployment lifecycle. Organizations using BOSH for infrastructure automation, particularly in cloud environments, face direct compromise of their entire director instance and downstream infrastructure.
While this CVE currently has no mapped MITRE ATT&CK techniques, Casky's Claude-powered analysis would identify the attack chain through credential-focused techniques: Adversary-in-the-Middle (T1557) enables the initial TLS interception, followed by Credential Dumping (T1110) when Basic-auth headers are harvested from unverified connections, and Unsecured Credentials (T1552.007) as rendered templates leak in plaintext. Practitioners using Casky would observe findings highlighting missing certificate pinning validations, unencrypted credential transmission during bootstrap, and overly permissive trust anchors in deployment manifests. Detection would flag anomalous DAV blobstore connections lacking proper certificate chains and identify rendered template archives being accessed by unexpected network paths—patterns indicating MitM exploitation rather than legitimate director initialization.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-47828. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation