01 / Carrier statement
Maersk reports unauthorised access to a legacy system
In an advisory dated 11 November 2026, Maersk says unauthorised access and data extraction affected a local legacy system inherited through an earlier acquisition. The carrier says it took action to secure the system and launched an investigation, which remains in progress.
Maersk's preliminary findings suggest that sensitive data has not been disclosed. The company reports no indication of an effect on its other systems or on customer and partner systems connected through API or EDI integrations. These are the carrier's findings at the time of its statement, rather than a completed independent assessment.
Maersk says it does not currently expect disruption to customer operations and that its platforms remain available for booking and shipment management. Reuters reported the same operational position on 11 November. The advisory does not give the dates of the intrusion or discovery; this report concerns the new public disclosure.
02 / Operational meaning
Keep shipment status separate from the investigation
The immediate planning point is that Maersk has not announced a customer booking-platform shutdown in this advisory. Its statement provides a basis for continuing normal shipment processes while checking for subsequent official updates.
Platform availability does not confirm every booking, cargo release or delivery appointment. Those still depend on the shipment's own accepted instructions, documentation and operational milestones. Equally, an investigation into a legacy application does not establish that a customer's connected system has been affected.
The carrier has not identified the particular acquisition or application in this notice, quantified the extracted data or announced a completion date for the investigation. Those gaps should remain unresolved in a shipment briefing. Do not substitute unverified claims for a carrier notification about a specific consignment or account.
03 / Shipment checks
Verify changed instructions before acting
Maersk specifically asks customers to verify unexpected communications about the incident through their usual company contact. The following workflow applies that instruction to freight handoffs; it is practical analysis, rather than an additional claim about the incident:
- Use the established channel. Open the carrier platform through an existing trusted route and use contact details already held by the shipment team. An unsolicited message should not become the source of a new contact or login route.
- Check what is being changed. Match the booking or bill-of-lading reference, cargo, requested action and responsible party. Verify unexpected requests to change document delivery, release instructions or payment details before acting.
- Record the operational confirmation. Keep the accepted instruction, confirmation time and responsible contact with the shipment file. If a platform transaction fails, check its status before resubmitting so the team avoids duplicate instructions.
- Escalate a specific exception. Where a booking, release or integration is actually failing, raise that identified problem with the carrier and the responsible internal team. The general advisory cannot diagnose an individual shipment's issue.
For an ocean-freight shipment, keep these confirmations aligned with cutoffs, document submission and the next cargo handoff. Continue to distinguish a verified operational exception from an unexpected message claiming to describe one.
04 / Sources
Dated disclosure and corroborating report
The English carrier advisory and Reuters report were read in full. Statements about system scope, data and expected operational impact are attributed to Maersk and remain preliminary while its investigation continues.
- Maersk: IT security incident — 11 November 2026.
- Reuters via WTAQ: Shipping firm Maersk investigates IT security incident — 11 November 2026.