Comparison Overview
DB Breweries

DB Breweries
Auckland, NZ
Last Update: 24/02/2026
DB Breweries is committed to Brewing a Better New Zealand by meeting ambitious sustainability targets that cover both environmental and social sustainability. DB operates out of our biggest production site, the Waitemata Brewery in Otahuhu, as well as Tuatara Brewery o...

JDE Peet's
Oosterdoksstraat 80, Amsterdam, North Holland, NL, 1011 DK
Last Update: 07/10/2026
JDE Peet’s is the world’s leading pure-play coffee company, serving approximately 4,400 cups of coffee per second in more than 100 markets. Guided by our ‘Reignite the Amazing’ strategy, we are focusing on brand-led growth across three big bets: Peet’s, L’OR, and Jacobs...
Compliance Ranges Comparison

DB Breweries







JDE Peet's






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for DB Breweries in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for JDE Peet's in 2026.
Incident History - DB Breweries (X = Date, Y = Severity)
DB Breweries cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JDE Peet's (X = Date, Y = Severity)
JDE Peet's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DB Breweries

JDE Peet's
FAQ
Latest Global CVEs
A security flaw has been discovered in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b. This affects the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. The manipulation of the argument imgsz/names/kpt_shape results in improper neutralization of directives in dynamically evaluated code. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypass per-IP rate limits on login, one-time passcode, and password validation endpoints, enabling brute-force attacks, and to falsify IP addresses recorded in audit logs.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can submit logins with the password "hunter2" and distinguish HTTP 403 from 401 responses to enumerate valid accounts and reveal the authentication provider of SSO-only users.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a stored HTML injection vulnerability because the ApplicationName and LogoURL appearance settings are rendered into HTML output without sufficient escaping. Attackers with the Owner role can store HTML markup in these settings that renders in the Coder dashboard and in SMTP notification emails sent to other deployment users.
Coder from 2.0.0 before 2.34.8 contains an open redirect vulnerability in handleAPIKeySmuggling that allows attackers to redirect users externally via unsanitized r.URL.Path values. Attackers can craft links on trusted workspace app subdomains with paths beginning with double slashes, which become scheme-relative redirects to attacker sites for phishing.