Linode Status
Real-time updates of Linode issues and outages
Linode status is Operational
Linode.com
Linode Cloud Manager and API
Linode Hosted DNS Service
Linode Longview
Linode Managed Databases
US-East (Newark)
US-Central (Dallas)
You're checking on Linode - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Recently Resolved Incidents
Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors.
This occurred as the result of an issue with a planned router upgrade. The router has since been brought back online, and we can confirm that the issue was mitigated at 10:19 UTC on May 29, 2026 and is no longer occurring.
We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. If you continue to experience problems, please open a Support ticket for assistance.
We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.
Linode Outage Survival Guide
Linode Components
Linode.com
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Cloud Manager and API
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Hosted DNS Service
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Longview
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Managed Databases
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Regions
Linode Metadata Service
US-East (Newark)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Central (Dallas)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-West (Fremont)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CA-Central (Toronto)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-West (London)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-South (Singapore)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Northeast-2 (Tokyo 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Southeast (Sydney)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (São Paulo)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo 3)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ZA-JNB (Johannesburg)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NZ-AKL (Auckland)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CO-BOG (Bogota)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-DEN (Denver)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-HAM (Hamburg)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-HOU (Houston)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
MY-KUL (Kuala Lumpur)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-MRS (Marseille)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
MX-QRO (Queretaro)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CL-SCL (Santiago)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR-2 (Paris 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD-2 (Washington 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Backups
US-East (Newark) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Central (Dallas) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-West (Fremont) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CA-Central (Toronto) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-West (London) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-South (Singapore) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Northeast-2 (Tokyo 2) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Southeast (Sydney) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (São Paulo) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo) Backups
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Block Storage
US-East (Newark) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Central (Dallas) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-West (Fremont) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CA-Central (Toronto) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-West (London) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-South (Singapore) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Northeast-2 (Tokyo 2) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Southeast (Sydney) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (São Paulo) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo 3) Block Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode NodeBalancers
US-East (Newark) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Central (Dallas) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-West (Fremont) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CA-Central (Toronto) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-West (London) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-South (Singapore) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Northeast-2 (Tokyo 2) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Southeast (Sydney) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (São Paulo) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo 3) NodeBalancers
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Object Storage
US-East (Newark) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai)
EU-West (London)
AP-South (Singapore) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (Sao Paulo) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors.
This occurred as the result of an issue with a planned router upgrade. The router has since been brought back online, and we can confirm that the issue was mitigated at 10:19 UTC on May 29, 2026 and is no longer occurring.
We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. If you continue to experience problems, please open a Support ticket for assistance.
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo 3) Object Storage
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Kubernetes Engine
US-East (Newark) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Central (Dallas) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-West (Fremont) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CA-Central (Toronto) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-West (London) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-South (Singapore) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Northeast (Tokyo 2) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Southeast (Sydney) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (São Paulo) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Metadata Service
US-East (Newark)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Central (Dallas)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-West (Fremont)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-Southeast (Atlanta)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-IAD (Washington)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-ORD (Chicago)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CA-Central (Toronto)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-West (London)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
EU-Central (Frankfurt)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-PAR (Paris)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-South (Singapore)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Northeast-2 (Tokyo 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-West (Mumbai)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AP-Southeast (Sydney)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SE-STO (Stockholm)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-SEA (Seattle)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IT-MIL (Milan)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-OSA (Osaka)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-MAA (Chennai)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ID-CGK (Jakarta)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
BR-GRU (São Paulo)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NL-AMS (Amsterdam)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-MIA (Miami)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-LAX (Los Angeles)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ES-MAD (Madrid)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
AU-MEL (Melbourne)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
GB-LON (London 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
IN-BOM-2 (Mumbai 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
SG-SIN-2 (Singapore 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-FRA-2 (Frankfurt 2)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
JP-TYO-3 (Tokyo 3)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
ZA-JNB (Johannesburg)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
NZ-AKL (Auckland)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
CO-BOG (Bogota)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-DEN (Denver)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
DE-HAM (Hamburg)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
US-HOU (Houston)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
MY-KUL (Kuala Lumpur)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
FR-MRS (Marseille)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
MX-QRO (Queretaro)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode ACLP Logs
CL-SCL (Santiago)
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
Linode Observability
US-LAX (Los Angeles) ACLP Logs
US-ORD (Chicago) ACLP Logs
Akamai Cloud Pulse (ACLP) - Alerts
Akamai Cloud Pulse (ACLP) - Logs
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems.
As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.
As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.
[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/