Vendor evidence profile
Akamai: what the public record shows
nexalign keeps a continuously updated evidence record on Akamai for network security decisions: 48 items from 4 kinds of source, covering April 2007 to July 2026. Every item on this page links to the source it came from, carrying the date that source states and saying so plainly where it states none.
In one line
This record holds 9 advisories attributed to Akamai products across 48 evidence items in total, none of them in the CISA catalogue of known exploited vulnerabilities. 100 percent of the record comes from sources Akamai cannot edit. Whether Akamai suits your decision is not on this page: that depends on your criteria, your compliance scope and your shortlist, and this record does not know them.
Evidence items
48
in this record
Attributed advisories
9
none known exploited
Authoritative share
69%
government registers
Last checked
Jul 18, 2026
sources re-queried
How independent is this record
Sources are not equal. A vendor can rewrite its own website overnight and optimise it for whatever a language model is likely to quote. It cannot edit a government vulnerability register or a years-old discussion thread. Every item in this record is classified by how much the vendor could influence it, and the score below is the weighted result.
Independence of this record
Objectivity score 88/100
- Authoritative
- 33 items, 69 percent
- Independent
- 15 items, 31 percent
- Vendor-controlled
- 0 items, 0 percent
100 percent of this record comes from sources Akamai does not control. The remainder is Akamai's own material and is marked as such wherever it appears.
Where this record comes from
These are the sources that contributed to the Akamai record, with the body that operates each one. No rating, score or ranking is taken from anywhere, and no vendor pays to appear in this index or to change what it says.
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| European Vulnerability Database | ENISA, European Union | Authoritative | 24 | May 08, 2026 |
| National Vulnerability Database | NIST, United States Department of Commerce | Authoritative | 9 | May 08, 2026 |
| Engineering discussions | Hacker News, public threads | Independent | 11 | Mar 07, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 4 | Jul 03, 2026 |
Documented vulnerabilities
Vulnerability registers are searched by keyword, so an advisory about a different product often mentions Akamai in passing. An entry is only listed here when a structural signal ties it to a product of Akamai: an advisory reference on the vendor's own domain, Akamai as the assigning authority, or the affected product list naming it. 9 records passed that test.
- CVE-2026-34354highCVSS 7.4May 08, 2026
Akamai Guardicore Platform Agent (GPA) and Zero Trust Client on Linux and macOS allow TOCTOU-based local privilege escalation.
- CVE-2026-26365mediumCVSS 4.0Feb 23, 2026
Akamai Ghost on Akamai CDN edge servers before 2026-02-06 mishandles processing of custom hop-by-hop HTTP headers, where an incoming request containing the header "Connection…
- CVE-2025-66373mediumCVSS 4.8Dec 04, 2025
Akamai Ghost on Akamai CDN edge servers before 2025-11-17 has a chunked request body processing error that can result in HTTP request smuggling.
- CVE-2025-53841highCVSS 7.8Dec 03, 2025
The GC-AGENTS-SERVICE running as part of Akamai´s Guardicore Platform Agent for Windows versions prior to v49.20.1, v50.15.0, v51.12.0, v52.2.0 is affected by a local privilege escalation…
- CVE-2025-54142mediumCVSS 4.0Aug 29, 2025
Akamai Ghost before 2025-07-21 allows HTTP Request Smuggling via an OPTIONS request that has an entity body, because there can be a subsequent request within the persistent connection…
- CVE-2025-32094mediumCVSS 4.0Aug 07, 2025
An issue was discovered in Akamai Ghost, as used for the Akamai CDN platform before 2025-03-26.
3 further attributed records are held in the pool. DecisionOS shows the full set against the components you actually run.
What practitioners report
Public threads in which engineers and administrators discuss running this product. Only threads naming Akamai in their own title are listed, so a discussion about someone else's incident cannot end up under this vendor. Not curated for sentiment: 11 threads in the record, most recent first.
- Hacker NewsMar 07, 2026Independent
Improving Antibot Biometric Protections: A Harsh Lesson from Akamai (2024)
- Hacker NewsDec 01, 2025Independent
Fermyon Joins Akamai
- Hacker NewsJul 27, 2025Independent
Linode / Akamai US-EAST is down
- Hacker NewsJun 30, 2025Independent
XML External Entity (XXE) Injection in Akamai CloudTest
- Hacker NewsMay 22, 2025Independent
Akamai, Microsoft Disagree on Severity of Unpatched 'BadSuccessor' Flaw
Independent coverage
Recognised analysts, review marketplaces and neutral technology press that name Akamai. This section runs on a fixed list of such outlets rather than on whatever a web search returns for the company name, because that search is dominated by sales-intelligence profiles and directory listings which say nothing about the product. Social networks and press-release wires are excluded outright.
- peerspot.comdate not recordedIndependent
Akamai Reviews, Competitors and Pricing
- en.wikipedia.orgdate not recordedIndependent
Akamai Technologies - Wikipedia
- gartner.comdate not recordedIndependent
Akamai Reviews, Ratings & Features 2026 | Gartner Peer Insights
- gartner.comdate not recordedIndependent
Akamai Guardicore Segmentation Reviews & Ratings 2026 | Gartner Peer Insights
What Akamai publishes about itself
The vendor's own documentation, kept separate from everything above and marked as vendor-controlled. It is useful, and it is a claim until an independent source confirms it.
What this record cannot tell you
A record is only trustworthy if it is explicit about its holes. These are the ones in the Akamai record right now.
A further 15 register entries mention Akamai without naming a product of Akamai as affected. They are excluded rather than counted as vulnerabilities.
Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Whether Akamai is the right choice is not on this page
A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.
Typical criteria for this category
Needs your case- Detection Accuracy (MITRE ATT&CK coverage)weight
- MDR / Managed Detection & Responseweight
- Deployment Complexityweight
- Automated Response / Remediationweight
- SIEM Integrationweight
Criteria shown as examples for network security. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.
What DecisionOS adds on top of this record
- The vendor scored against your criteria with your weighting, not against a generic ranking
- A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
- A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
- This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
- A decision memo your board can read, with the trade-offs and the reasoning on the record
Questions this page answers
Is Akamai a safe choice?
The public record holds 9 advisories attributed to Akamai products and 48 evidence items in total. None of them appears in the CISA catalogue of known exploited vulnerabilities. Whether that is acceptable depends on your risk appetite, your compliance scope and the alternatives on your shortlist, none of which a public page can know. This page reports the record; it does not rate the vendor.
Where does the Akamai data on this page come from?
From 4 kinds of source: European Vulnerability Database, operated by ENISA, European Union; National Vulnerability Database, operated by NIST, United States Department of Commerce; Engineering discussions, operated by Hacker News, public threads; Analyst, review and reference sources, operated by Recognised analysts, review marketplaces and technology press. Every item carries its source URL and, where the source states one, its date.
Does Akamai pay to appear in this index?
No. There is no paid placement, no sponsored profile and no way for a vendor to change what the record says. Vendors are listed because their category comes up in enterprise technology decisions. Corrections to a specific entry can be sent to [email protected] and are checked against the source.
How much of the Akamai record is the vendor's own material?
0 percent. The remaining 100 percent comes from sources Akamai does not control. Vendor-published material stays in the record and is labelled as vendor-controlled rather than counted as independent confirmation.
Why does this page not say whether Akamai is better than the alternatives?
Because better only exists relative to a decision. Which criteria matter, how heavily each one weighs and what counts as a dealbreaker are properties of the buyer, not of the vendor. DecisionOS takes this same evidence pool and scores it against the criteria of an actual decision, which is where a comparison becomes meaningful.
How this record is built
Sources are queried on a schedule, not on request. Findings are stored with the source URL, the event date and a content hash, so the same item is never counted twice and every statement stays traceable to where it came from.
Nothing on this page is written by a language model. Counts are counts, dates are the dates the sources carry, and titles are the sources' own wording. Where a section is empty, that is a finding in itself and is stated as one.
Corrections are welcome. If an entry is wrong or an attribution is off, write to [email protected] and it gets checked against the source.
Citing this page
nexalign GmbH, Akamai: what the public record shows, nexalign vendor evidence index, Jul 18, 2026. Available at nexalign.io/vendors/akamai.
Other vendors in network security
The whole field is on one page: every network security vendor with a published record, with the size of each.
Check Point
137 evidence items from 5 sources
Fortinet
130 evidence items from 5 sources
Palo Alto Networks
116 evidence items from 5 sources
Cisco Security
93 evidence items from 5 sources
Juniper Networks
86 evidence items from 6 sources
SonicWall
73 evidence items from 6 sources
Turn this record into a decision you can defend
DecisionOS takes the same evidence pool this page is built from, weighs it against the criteria of your actual decision, and produces a memo that holds up in front of a board and an auditor.