Vulnerability in BOSH (CVE-2026-41860)
Summary
Vulnerability in BOSH (CVE-2026-41860). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 282.1.9 or later.
Original description
The description as published by the source.
CWE-326 in BOSH allows a local attacker to steal Basic-auth credentials or redirect UAA token requests via MITM. HttpRequestHelper#create_async_endpoint and #send_http_get_request_synchronous hard-code OpenSSL::SSL::VERIFY_NONE, enabling an attacker to intercept traffic between bosh-monitor and the BOSH director or UAA and steal credentials.
Affected versions:
- BOSH: all versions prior to v282.1.9 (inclusive); fixed in v282.1.9 or later
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41860 has been found in BOSH.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade BOSH to 282.1.9 or later.
If unsure, ask your IT team or search "BOSH CVE-2026-41860" on the vendor's site.
CVE-2026-41860 (BOSH) — CWE-326 / CVSS v3 8.8
Attack vector: local / no user interaction
Patched: 282.1.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-326) exists in BOSH.
Check the vendor advisory for the affected versions of BOSH.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 282.1.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'BOSH' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'BOSH' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
BOSHを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade BOSH to 282.1.9ステージング環境で 282.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web cloudfoundry.org
- web github.com
- web security@vmware.com