Comparison Overview
Staccato

Staccato
114 Halmar Cove, Georgetown, 78628, US
Last Update: 01/05/2026
Americans who protect loved ones, communities, our Country, and way of life choose Staccato. These heroes shoot their best with our 2011® pistols. Based in the heart of Texas, we are veteran-led and over 25% of our team has served our country. Driven to deliver the bes...

New Balance
100 Guest St, Brighton Landing, Brighton, MA, US, 02135-2088
Last Update: 02/04/2026
In 1906, New Balance began as a humble one-man operation founded on the belief that “we were born to move,” and has since grown into an international corporation, selling footwear and apparel in over 120 countries and employing over 14,000 associates worldwide. Our miss...
Compliance Ranges Comparison

Staccato







New Balance






Benchmark & Cyber Underwriting Signals
Incidents vs Sporting Goods Manufacturing Industry Avg (This Year)
No incidents recorded for Staccato in 2026.
Incidents vs Sporting Goods Manufacturing Industry Avg (This Year)
No incidents recorded for New Balance in 2026.
Incident History - Staccato (X = Date, Y = Severity)
Staccato cyber incidents detection timeline including parent company and subsidiaries.
Incident History - New Balance (X = Date, Y = Severity)
New Balance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Staccato

New Balance
FAQ
Latest Global CVEs
A flaw has been found in sigoden aichat up to 0.30.4. This affects an unknown function of the file src/serve.rs of the component API Endpoint. This manipulation causes uncontrolled memory allocation. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was detected in rowboatlabs rowboat up to 0.9.1. The impacted element is the function request.text/req.json of the file apps/rowboat/app/api/composio/webhook/route.ts of the component Composio Webhook Endpoint. The manipulation results in denial of service. It is possible to launch the attack remotely. The exploit is now public and may be used. Upgrading to version 0.9.2 is sufficient to resolve this issue. Upgrading the affected component is recommended. The legacy Next.js app was deleted at 0.9.2 rather than patched, leaving no security control behind.
A security vulnerability has been detected in Reader Tools PDF Reader App 98.8 on Android. The affected element is the function ActSplashNew.handleDeeplink of the component File Handler. The manipulation of the argument _display_name leads to path traversal. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Windows ML CLI is a command line tool for building portable, performant, and high-quality AI models for Windows ML. Prior to 0.4.0, the src/winml/modelkit/serve/cli_api.py component exposes WinML CLI commands through a localhost HTTP API without authentication and configures the allow_origins setting as a wildcard in both src/winml/modelkit/serve/cli_api.py and src/winml/modelkit/serve/app.py. A malicious website loaded by a user can send cross-origin requests to /v1/cli/build or /v1/cli/config and set the trust_remote_code parameter to true, which is converted to the --trust-remote-code command-line flag without validation. This reaches AutoConfig.from_pretrained with trust_remote_code=True in src/winml/modelkit/loader/_autoconfig.py and imports Python code from an attacker-controlled model repository, resulting in arbitrary code execution as the server user. This issue is fixed in version 0.4.0.
fast-uri serializes the port component of a URI without validating it. When recomposing the authority, the userinfo and host components are escaped but the port is concatenated verbatim, so a port value that is not a sequence of digits can inject authority delimiters, demoting the intended host to userinfo and pointing the authority at an attacker-controlled host. Both fast-uri and Node's URL read the result back as the attacker's host with no error, so re-validating the built URI does not catch it. This affects applications that build URIs from parts and assign untrusted data to the port component through the serialize, normalize, or equal functions in their object forms. The issue affects fast-uri versions before 2.4.6, from 3.0.0 before 3.1.7, and from 4.0.0 before 4.1.4. It is fixed in 2.4.6, 3.1.7, and 4.1.4, where recomposeAuthority rejects any port that is not a digit sequence per RFC 3986.