View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Wed, 18 Nov 2026 09:31:33 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 09:31:33 GMT |
| Seen by Spike | Wed, 18 Nov 2026 09:35:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | investigating | Direct: Akamai status page · source ↗ |
| affected services | Customer Security Advisory | Direct: Akamai status page · source ↗ |
| Cause | Akamai has not stated a cause in a structured field. Read the provider's updates. | |
| Customer impact | Depends on what you run. Spike Pro matches this incident to the services a workspace lists. | |
Revisions, newest first
- Revision 1 · Incident opened
Published by Akamai 2026-11-18 09:31 UTC · seen by Spike 4 min laterAkamai said: “Akamai is aware of the recently identified Java4Shell Remote Code Execution (RCE) vulnerability, tracked as CVE-2026-114938.We are actively assessing the potential impact of this vulnerability across our platform and services. Our security teams are engaged and are taking…”