Comparison Overview
AHM (Advanced Health Media)

AHM (Advanced Health Media)
420 Mountain Avenue, New Providence, New Jersey, US, 07974
Last Update: 05/04/2026
Founded in 1999, AHM, an IQVIA company, is a leading global provider of software and services to manage compliant healthcare professional (HCP) engagements. The spectrum of AHM’s customer base extends from emerging Life Sciences companies to 11 of the Top 20 global phar...

Mphasis
Mphasis Limited, Bagmane Laurel, 1st Floor, Tower A, , Bagmane Technology Park, C V Raman Nagar, Bangalore, Karnataka, IN, 560093
Last Update: 02/04/2026
A leading applied technology services company, we innovate to deliver service excellence and successful outcomes across sales, delivery and development. With our strategy to be agile, nimble and customer-centric, we anticipate the future of applied technology and predic...
Compliance Ranges Comparison

AHM (Advanced Health Media)







Mphasis






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for AHM (Advanced Health Media) in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Mphasis in 2026.
Incident History - AHM (Advanced Health Media) (X = Date, Y = Severity)
AHM (Advanced Health Media) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mphasis (X = Date, Y = Severity)
Mphasis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AHM (Advanced Health Media)

Mphasis
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: *.*.