Comparison Overview
Trimble ProjectSight
Trimble ProjectSight
10368 Westmoor Dr, Westminster, Colorado, 80021, US
Last Update: 23/04/2026
Dedicated to the world’s tomorrow, Trimble is a technology company delivering solutions that enable our customers to work in new ways to measure, build, grow and move goods for a better quality of life. Core technologies in positioning, modeling, connectivity and data a...
Atlassian
Level 6/341 George St, Sydney, 2000, AU
Last Update: 18/09/2026
Atlassian powers the collaboration that helps teams accomplish what would otherwise be impossible alone. From space missions and motor racing to bugs in code and IT requests, no task is too large or too small with the right team, the right tools, and the right practice...
Compliance Ranges Comparison
Trimble ProjectSight
Atlassian
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Trimble ProjectSight in 2026.
Incidents vs Software Development Industry Avg (This Year)
Atlassian has 385.44% more incidents than the average of all companies with at least one recorded incident.
Incident History - Trimble ProjectSight (X = Date, Y = Severity)
Trimble ProjectSight cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Atlassian (X = Date, Y = Severity)
Atlassian cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Trimble ProjectSight
Atlassian
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout