
Berkshire Hathaway
None



None

As one of the largest global insurers, our purpose is to act for human progress by protecting what matters. Protection has always been at the core of our business, helping individuals, businesses and societies to thrive. And AXA has always been a leader, an innovator, an entrepreneurial company, fostering progress in all its dimensions. Our purpose also links back to the Group's roots. From the outset, AXA has been committed to acting as a force for collective good. From solidarity-based actions with AXA Hearts In Action to work on prevention issues with the AXA Research Fund and the fight against climate change, AXA has always been attentive to its social environment and embraced its responsibility as an insurer: responsibility for taking action upstream in order to better understand risks, with one goal in mind: to ensure better protection. Discover more: https://www.axa.com/en/about-us/our-purpose To know more about AXA's Privacy Policy - https://www-axa-com.cdn.axa-contento-118412.eu/www-axa-com/1cd44dfb-3b7a-4cf7-933b-06024cf7f25b_axa_privacypolicy_internetusers_va.pdf
Security & Compliance Standards Overview












No incidents recorded for Berkshire Hathaway in 2025.
No incidents recorded for AXA in 2025.
Berkshire Hathaway cyber incidents detection timeline including parent company and subsidiaries
AXA cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.
uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.
A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.
A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).