Transforming air mobility through software and electrification.
Lufthansa is one of the world’s leading airlines, connecting passengers to over 200 destinations across 74 countries from our hubs in Frankfurt and Munich. As an industry pioneer, we are committed to shaping the future of sustainable aviation, investing in next-generation aircraft, cutting-edge technology, and digital solutions. Our goal is to drive excellence: not just in the sky, but across every touchpoint of the travel experience. With Lufthansa Allegris, our new long-haul experience, we are setting a new standard in premium travel, introducing a completely redesigned First, Business, Premium Economy, and Economy Class for ultimate comfort and choice. We continue to enhance the travel experience with state-of-the-art lounges, award-winning service, and onboard broadband Wi-Fi (FlyNet) across our entire long-haul fleet. Follow us for updates on how we're shaping the future of aviation. For more information, reservations or customer service, visit lufthansa.com or follow us on Facebook, X and Instagram. We look forward to welcoming you onboard. This LinkedIn page is maintained by Deutsche Lufthansa AG. We will not answer specific Customer Service queries here on LinkedIn. If you have an immediate concern or need to contact us please visit http://www.lufthansa.com/us/en/imprint
Security & Compliance Standards Overview
No incidents recorded for Surf Air Mobility in 2025.
No incidents recorded for Lufthansa in 2025.
Surf Air Mobility cyber incidents detection timeline including parent company and subsidiaries
Lufthansa cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.
Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.
Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.
Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.
