Comparison Overview
Bose Corporation

Bose Corporation
The Mountain Rd, Framingham, Massachusetts, 01701, US
Last Update: 02/04/2026
Bose Corporation was founded in 1964 by Dr. Amar G. Bose, then a professor of electrical engineering at the Massachusetts Institute of Technology. Today, the company is driven by its founding principles, investing in long-term research with one fundamental goal: to deve...

Garmin
1200 E. 151st Street, Olathe, KS, US, 66062
Last Update: 27/04/2026
WHERE DO WE START? How about Kansas City? That’s our home. That’s where Garmin put a stake in the ground in 1989. We’ve grown substantially over the years, offering diverse products and global reach in 5 diverse markets. But some things won’t ever change: Our entreprene...
Compliance Ranges Comparison

Bose Corporation







Garmin






Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Bose Corporation in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Garmin has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Bose Corporation (X = Date, Y = Severity)
Bose Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Garmin (X = Date, Y = Severity)
Garmin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bose Corporation

Garmin
FAQ
Latest Global CVEs
knowns versions before 0.30.0 contain an authorization bypass vulnerability where mutating code actions are incorrectly classified as read-only operations. Attackers with read-restricted sessions can exploit code.replace to modify permission configurations and escalate privileges on subsequent calls.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/permissions/guard.go#L44-L60
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/permissions/registry.go#L99-L140
- https://github.com/knowns-dev/knowns/commit/a2c98fc5c313463576c9348beeec6a74ddd7333b
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-w323-3wpx-f7g5
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-authorization-bypass-via-misclassified-code-actions
knowns versions before 0.30.0 serve the management API without authentication on all network interfaces by default, with no password required on fresh installations. Attackers can access the unauthenticated /api/tunnel/start endpoint to provision a public tunnel and republish the API at a publicly accessible address.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/cli/browser.go#L193-L200
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/auth.go#L80-L86
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/tunnel.go#L26-L38
- https://github.com/knowns-dev/knowns/commit/878a02cb7cc14f0a592fdfda7a520af3cac500fb
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-fc85-99vc-9c75
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-unauthenticated-management-api-exposure
knowns before 0.30.0 fails to validate import names in the import routes, allowing unauthenticated attackers to write files outside the imports directory. Attackers can supply traversal sequences in the name parameter to escape the imports directory and overwrite arbitrary files writable by the server process.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/imports.go#L376-L420
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/imports.go#L519-L551
- https://github.com/knowns-dev/knowns/commit/d3989829fb5095666d23d005b2f78a082832a396
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-wh3c-v55g-qfg8
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-path-traversal-via-import-name
knowns versions before 0.30.0 contain a path traversal vulnerability in the handleCodeReplace() function that allows attackers to overwrite arbitrary files outside the project root. Attackers can supply absolute paths or relative paths containing directory traversal sequences to write malicious content to sensitive files like shell startup scripts or SSH configuration files.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/mcp/handlers/code.go#L588-L646
- https://github.com/knowns-dev/knowns/commit/a2c98fc5c313463576c9348beeec6a74ddd7333b
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-f539-xgc6-xw7q
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-path-traversal-via-code-replace-mcp-action
knowns versions before 0.30.0 fail to validate the settings.lsp.languages binary field in project configuration files, allowing attackers to execute arbitrary binaries by crafting a malicious .knowns/config.json file. When a repository with a crafted configuration is opened, the unvalidated binary path is executed twice under the user's account without any verification.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/lsp/detect.go#L128-L157
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/models/config.go#L205-L216
- https://github.com/knowns-dev/knowns/commit/d3989829fb5095666d23d005b2f78a082832a396
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-mc52-mwq4-vfx3
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-arbitrary-code-execution-via-lsp-binary