Comparison Overview
Yanmar Brasil

Yanmar Brasil
Avenida Eduardo Borsari, Indaiatuba, 13347-320, BR
Last Update: 01/05/2026
Fundada em 1912, no Japão, com o nome de Yamaoka Hatsudoki Kosakusho, nove anos mais tarde, quando teve seu primeiro motor a diesel fabricado, passou a chamar-se YANMAR. No Brasil sua história começou em 1957, com a fundação da subsidiária Yanmar Diesel do Brasil Ltda, ...

John Deere
Moline, 61265, US
Last Update: 01/04/2026
It doesn’t matter if you’ve never driven a tractor, mowed a lawn, or operated a dozer. With John Deere’s role in helping produce food, fiber, fuel, and infrastructure, we work for every single person on the planet. It all started nearly 200 years ago with a steel plow...
Compliance Ranges Comparison

Yanmar Brasil







John Deere






Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Yanmar Brasil in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for John Deere in 2026.
Incident History - Yanmar Brasil (X = Date, Y = Severity)
Yanmar Brasil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - John Deere (X = Date, Y = Severity)
John Deere cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Yanmar Brasil

John Deere
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.