Improper TLS certificate validation in BOSH bosh-monitor
CVE-2026-41860 is a vulnerability in BOSH, specifically in bosh-monitor, caused by hard-coded use of OpenSSL::SSL::VERIFY_NONE in the HttpRequestHelper#create_async_endpoint and HttpRequestHelper#send_http_get_request_synchronous methods. This disables TLS certificate verification for outbound HTTPS connections, allowing an attacker positioned to intercept local network traffic to perform a man-in-the-middle attack against communications between bosh-monitor and the BOSH Director or UAA. As a result, the attacker can observe or tamper with protected traffic, including stealing Basic-auth credentials and redirecting UAA token requests. The issue affects all BOSH versions prior to 282.1.9 and is fixed in 282.1.9 and later.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.