Comparison Overview
L&S Mechanical
L&S Mechanical
1101 E Arapaho Rd, Richardson, 75081, US
Last Update: 04/04/2026
L&S Mechanical began as a Dallas-based contractor in 1985 and has grown over the years to have six locations out of Dallas, Fort Worth, Houston, San Antonio, and Austin. Over the past thirty years, we have become known as the premier provider of new home construction i...
Burns & McDonnell
9400 Ward Pkwy, Kansas City, 64114, US
Last Update: 02/04/2026
At Burns & McDonnell, our engineers, construction professionals, architects, planners, technologists and scientists do more than plan, design and construct. With a mission unchanged since 1898 — make our clients successful — we partner with you on the toughest challenge...
Compliance Ranges Comparison
L&S Mechanical
Burns & McDonnell
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
L&S Mechanical has 52.38% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Burns & McDonnell in 2026.
Incident History - L&S Mechanical (X = Date, Y = Severity)
L&S Mechanical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Burns & McDonnell (X = Date, Y = Severity)
Burns & McDonnell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
L&S Mechanical
Burns & McDonnell
FAQ
Latest Global CVEs
Improper access control in Microsoft Edge for Android allows an unauthorized attacker to bypass a security feature over a network.
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. Affected is the function GatewayStreamConsumer._filter_and_accumulate of the file gateway/stream_consumer.py of the component Streaming Reasoning Tag Filter. The manipulation leads to improper handling of case sensitivity. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project decided to not implement a dedicated fix: "[T]he analysis and the fix are both sound. It just lands below the bar for the maintenance cost of a duplicated scrub path."
- https://gist.github.com/YLChen-007/2229e5505bcbb3e15a7ae8fba4c4be37
- https://github.com/NousResearch/hermes-agent/
- https://github.com/NousResearch/hermes-agent/issues/27288
- https://github.com/NousResearch/hermes-agent/pull/28631#issuecomment-4622188016
- https://vuldb.com/cve/CVE-2026-14617
- https://vuldb.com/submit/844654
- https://vuldb.com/vuln/376134
- https://vuldb.com/vuln/376134/cti
Insufficient ui warning of dangerous operations in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Relative path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.