Yokogawa Electric Corporation is an electrical/electronic manufacturing company based out of Not Available, Not Available, Not Available, Italy.
At Dyson we are focused on solving the problems that others have ignored; solving them first using our technology and ingenuity. In order to achieve this we need to pioneer technologies that are different and authentic. This is the core of what we do and who we are. We must strive to create the future, every single day by developing new things, different things, things that go against the grain with a diverse and global team of ingenious minds. Dyson employs over 14,000 people and is present in more than 80 countries. And while we are growing fast we want Dyson to remain a start-up in spirit with the freedom of experimentation and learning, constantly reinventing our products as well as reinventing how we work, how we sell and how we support our owners. At the same time we are working through the James Dyson Foundation, James Dyson Award and Dyson Institute to inspire future engineers and pioneering a new approach to engineering education. Underlining everything we do in this diverse environment is the need to always show respect, supporting each other as one team to overcome whatever challenges we encounter. We drive empowerment, development and equality in an inclusive environment for our people around the world. The future doesn’t just happen, we look to make it happen, to achieve leaps through pioneering new ideas.
Security & Compliance Standards Overview
Yokogawa Electric Corporation has 17.65% more incidents than the average of same-industry companies with at least one recorded incident.
No incidents recorded for Dyson in 2025.
Yokogawa Electric Corporation cyber incidents detection timeline including parent company and subsidiaries
Dyson cyber incidents detection timeline including parent company and subsidiaries
httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.
5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.
continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.
LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3
LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.
