Summary
PX4 Autopilot versions 1.12.x through 1.15.x contain a logic flaw in the mode switching mechanism that fails to validate throttle stick position when changing from Auto mode to Manual mode while the drone is still ARMED after landing.
Under these conditions, the aircraft can abruptly apply high throttle on entering Manual mode, potentially causing loss of control, rapid uncontrolled ascent (flyaway), and property damage.
Affected context
This vulnerability appears in PX4-based multicopters or similar VTOL platforms using firmware versions 1.12.x through 1.15.x, where flight mode transitions between Auto and Manual are supported.
It is specifically relevant when:
- The vehicle is in Auto mode and has just completed a landing sequence
- The vehicle remains in the ARMED state, awaiting automatic disarm per the COM_DISARM_LAND parameter
- A pilot or system command initiates a switch from Auto to Manual mode during this ARMED-but-on-ground interval
In this context, the absence of a throttle stick position safety check on mode switch can cause unexpected motor output.
Exploit preconditions
- Attack surface: Flight control logic governing mode transitions and throttle handling.
- Required access: Ability to command a flight mode change from Auto to Manual (e.g., via RC transmitter, GCS, or integrated control system) while the drone remains ARMED after landing.
- Trigger point:
- The drone completes an Auto landing and stays ARMED (COM_DISARM_LAND has not yet triggered).
- A mode switch to Manual is requested while the physical throttle stick may be at a high or non-idle position.
- Why exploitation is possible: The firmware does not enforce a throttle threshold or "throttle-safe" condition at the moment of switching from Auto to Manual in this specific ARMED, post-landing state, allowing the system to interpret the current stick position as immediately valid throttle input.
Why this happens
The root cause is an incomplete authorization and safety gating check on a critical state transition in the flight control logic.
When transitioning from Auto to Manual mode while ARMED on the ground, the firmware should validate that the physical throttle stick is at or below a defined safe threshold before accepting it as a live control input.
This missing guard aligns with CWE-862: Missing Authorization, where a sensitive operation—in this case, engaging manual throttle authority on armed motors—is performed without verifying that all necessary preconditions (throttle-safe state) are satisfied.
Conceptually, the control flow trusts the current RC input without re-qualification during mode change, creating a narrow but dangerous window where previously benign input becomes hazardous in the new mode.
Potential impact
- The drone may suddenly spool up motors and apply high thrust immediately after switching to Manual mode.
- The aircraft could experience a rapid, uncontrolled ascent (flyaway) from the ground or low altitude.
- Pilots may temporarily lose control authority or require emergency actions to regain stability.
- Property damage can occur if the drone collides with nearby structures, vehicles, or other equipment.
- In crowded environments, there is potential for safety hazards to people in the vicinity of the landing area.
General mitigation guidance
Mitigation typically focuses on enforcing explicit safety gates around mode transitions and input acceptance:
- Introduce a throttle-safe check on all transitions into Manual (and similar direct-input) modes, requiring the throttle stick to be at or below a configured threshold before arming throttle output.
- Implement a "latched" disarm or motor-safe state after Auto landing that must be consciously cleared by the operator with known-safe stick positions or specific commands.
- Ensure mode-switch logic normalizes or ignores throttle input until both the aircraft state (e.g., landed) and RC inputs meet safe criteria, then gradually hands over control.
- Use configuration defaults that minimize motor authority immediately after landing, particularly while the vehicle remains ARMED.
- Encourage operational procedures where pilots return throttle to idle before changing from Auto to Manual mode, and validate that documentation and UI clearly communicate this requirement.
How teams detect issues like this
Effective detection focuses on reviewing control logic around state transitions and safety interlocks:
- Perform code review on mode-switch handlers and arming logic to confirm that every transition into Manual or high-authority modes includes:
- RC input validation (especially throttle)
- State checks (e.g., landed vs. flying)
- Explicit motor output gating where needed
- Use static analysis or rule-based checks to flag control paths where:
- Motor outputs become directly responsive to RC input without preceding safety conditions.
- Critical transitions reuse input without re-validating thresholds when modes change.
- Incorporate simulation-based regression tests that:
- Reproduce Auto landing to ARMED-on-ground states.
- Systematically issue mode changes under varying throttle positions and verify that motor outputs remain safe.
- Extend safety and compliance policies to require documented preconditions for any operation that can increase thrust, and periodically audit firmware implementations against these policies.

