Comparison Overview
Targeted Oncology

Targeted Oncology
2 Clarke Dr, Cranbury Township, New Jersey, undefined, US
Last Update: 08/03/2026
TargetedOnc.com provides content focused on next generation therapeutics and their molecular targets. As the field of oncology continues to trend toward systemic biology and molecular aberrations, the challenge facing many oncologists is staying recent and up-to-date wi...

Vox Media
Washington, DC, US, 20036
Last Update: 30/03/2026
Vox Media, the leader in modern media, is home to a portfolio of top talent and engaging editorial brands that ignite conversations and set trends, including Eater, Vox, The Verge, SB Nation, The Dodo, New York Magazine, The Cut, and Vulture. The company’s podcast netwo...
Compliance Ranges Comparison

Targeted Oncology







Vox Media






Benchmark & Cyber Underwriting Signals
Incidents vs Online Audio and Video Media Industry Avg (This Year)
No incidents recorded for Targeted Oncology in 2026.
Incidents vs Online Audio and Video Media Industry Avg (This Year)
No incidents recorded for Vox Media in 2026.
Incident History - Targeted Oncology (X = Date, Y = Severity)
Targeted Oncology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vox Media (X = Date, Y = Severity)
Vox Media cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Targeted Oncology

Vox Media
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.