Comparison Overview
Special Dog Company

Special Dog Company
Chácara Santa Amália, s/nº, Santa Cruz do Rio Pardo, São Paulo, BR, 18919-899
Last Update: 04/02/2026
Special Dog Company was born in February 2001 in the city of Santa Cruz do Rio Pardo, São Paulo State. Thanks to the desire to feed cats and dogs high quality food with the affection they deserve, the company quickly became one of the largest industries in the business ...

Lee Kum Kee
2-4 Dai Fat St, Tai Po Industrial Estate, Tai Po, Hong Kong, HK
Last Update: 01/04/2026
Established in 1888, Lee Kum Kee is an international household name in authentic Asian sauces and condiments, as well as “a symbol of quality and trust”. As a globally renowned Chinese multinational corporation, Lee Kum Kee now offers over 200 types of sauce and condime...
Compliance Ranges Comparison

Special Dog Company







Lee Kum Kee






Benchmark & Cyber Underwriting Signals
Incidents vs Food Production Industry Avg (This Year)
No incidents recorded for Special Dog Company in 2026.
Incidents vs Food Production Industry Avg (This Year)
No incidents recorded for Lee Kum Kee in 2026.
Incident History - Special Dog Company (X = Date, Y = Severity)
Special Dog Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lee Kum Kee (X = Date, Y = Severity)
Lee Kum Kee cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Special Dog Company

Lee Kum Kee
FAQ
Latest Global CVEs
mem0's openmemory/api component contains an unauthenticated access vulnerability that allows unauthenticated attackers to read, write, and delete arbitrary user memories by accessing API routers registered without authentication middleware. Attackers can supply arbitrary user_id parameters or directly access memory retrieval endpoints to expose private memory content, or invoke pause endpoints with global_pause=true to cause denial-of-service across all users.
Cap's GET /api/video/ai endpoint fails to validate user ownership or membership before returning private video AI metadata including titles, summaries, and chapters. Authenticated attackers can supply arbitrary video IDs to read sensitive AI-generated content and trigger unauthorized AI generation that consumes the video owner's credits without consent.
Coder allows organizations to provision remote development environments via Terraform. Starting in version 2.17.0 and prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, `POST /api/v2/files` converts zip uploads to tar in memory via `CreateTarFromZip`, which enforced a per-entry size limit but no aggregate limit on total decompressed output, writing to an unbounded in-memory buffer. Exploitation requires authenticated file-upload access and the impact is limited to availability (denial of service). The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 adds a metadata preflight check that sums projected entry sizes and a streaming writer that enforces the aggregate limit during decompression. As a workaround, restrict file-upload permissions to trusted users or place a reverse proxy with request-body size limits in front of `coderd`.
- https://github.com/coder/coder/pull/25877
- https://github.com/coder/coder/releases/tag/v2.29.17
- https://github.com/coder/coder/releases/tag/v2.32.7
- https://github.com/coder/coder/releases/tag/v2.33.8
- https://github.com/coder/coder/releases/tag/v2.34.2
- https://github.com/coder/coder/security/advisories/GHSA-2mg2-p7r7-g27f
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, the `PUT /api/v2/users/{user}/password` endpoint authorized only `ActionUpdatePersonal` and did not prevent a `user-admin` from resetting an `owner` account's password. It also did not require the current password when an admin reset another user's password. Exploitation requires the privileged `user-admin` role so practical risk is limited to deployments that grant `user-admin` to less trusted operators. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 prevents non-owner users from resetting the password of an account that holds the `owner` role. As a workaround, restrict the `user-admin` role to trusted administrators.
- https://github.com/coder/coder/pull/25709
- https://github.com/coder/coder/releases/tag/v2.29.17
- https://github.com/coder/coder/releases/tag/v2.32.7
- https://github.com/coder/coder/releases/tag/v2.33.8
- https://github.com/coder/coder/releases/tag/v2.34.2
- https://github.com/coder/coder/security/advisories/GHSA-29xf-69gq-m9jx
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, Coder's OIDC callback checked `email_verified` with a direct Go `bool` type assertion. When an IdP returned the claim as a non-boolean (for example the string `"false"`) or omitted it, the assertion failed open and the email was treated as verified. Combined with an unconditional email-based account fallback, this enabled account takeover. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 coerces `email_verified` across bool, string and numeric types (fail-closed) and blocks the email fallback when the matched user already has a different linked IdP subject. As a workaround, ensure the IdP returns `email_verified` as a native JSON boolean. The email-fallback linking issue has no configuration workaround; upgrading is required.
- https://github.com/coder/coder/pull/25712
- https://github.com/coder/coder/pull/25713
- https://github.com/coder/coder/releases/tag/v2.29.17
- https://github.com/coder/coder/releases/tag/v2.32.7
- https://github.com/coder/coder/releases/tag/v2.33.8
- https://github.com/coder/coder/releases/tag/v2.34.2
- https://github.com/coder/coder/security/advisories/GHSA-75vm-6w67-gwvp