Comparison Overview
PagerDuty

PagerDuty
600 Townsend Street, San Francisco, 94103, US
Last Update: 04/04/2026
In an always-on world, teams trust PagerDuty to help them deliver an optimal digital experience to their customers, every time. PagerDuty is the central nervous system for a company’s digital operations. We identify issues and opportunities in real-time and bring togeth...

Autodesk
Market St, San Francisco, CA, US, 94105
Last Update: 14/09/2026
Autodesk is changing how the world is designed and made. Our technology spans architecture, engineering, construction, product design, manufacturing, and media and entertainment. We empower innovators everywhere to solve challenges, big and small. From greener buildi...
Compliance Ranges Comparison

PagerDuty







Autodesk






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for PagerDuty in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Autodesk in 2026.
Incident History - PagerDuty (X = Date, Y = Severity)
PagerDuty cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Autodesk (X = Date, Y = Severity)
Autodesk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PagerDuty

Autodesk
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.