August 24, 2026 PX4 Weekly Dev Update: Hardware Expansion, System Stabilization, and MAVLink Security Enhancements

Dear PX4 community developers, this is the PX4 weekly integrated briefing for August 24, 2026. Over the past week, the PX4 Autopilot project has shown significant activity, focusing on extensive hardware support expansion, core system stabilization, and several critical bug fixes. Notably, the addition of new flight control boards and sensor drivers stood out, alongside continuous efforts to improve simulation environments and enhance the precision of flight control algorithms.

Of particular note are several security vulnerabilities discovered in the MAVLink protocol and the GPS NMEA parser, which underscore the need for ongoing attention to the robustness and safety of drone systems. Furthermore, the release of QGroundControl’s latest stable version and active discussions in the developer forum demonstrate the growing maturity of the PX4 ecosystem. Overall, the development team continues to maintain a balanced approach, extending functionality while simultaneously enhancing system reliability.

PX4 Releases and Key Changes per Version

While there were no new official releases in the past 7 days, the most significant recent pre-release, v1.18.0-beta2 (published August 09, 2026), is currently the focus of testing and feedback from the developer community. This version addresses critical issues found after v1.18.0-beta1, significantly improving stability.

• v1.18.0-beta2 (Details)
  • Fixed-wing Control Improvements: Addressed NaN eas2tas bug in lat/lon control and malfunctions due to incorrect attitude frame in Tailsitter.
  • QGC Compatibility Restored: Resolved QGC compatibility issues caused by stricter command validation for multicopter guided takeoff, camera mission items, and VTOL landing patterns.
  • Hardware and Driver Stabilization: Enhanced hardware reliability by fixing SD card read errors on STM32H7 boards, FMUv6X-RT FRAM multi-page writes, and FlexSPI DLL calibration issues. Several fixes for the BMP388 driver were also included.
  • Estimator Improvements: Corrected hard reset issues in external position estimation and faulty data fusion errors from DroneCAN rangefinders.
  • Battery Management and Commander Features: Resolved RTL trigger issues when battery remaining percentage is unknown, improved Coulomb counting accuracy, and added/improved multicopter autotune rerun functionality.
  • MAVLink and Build Optimization: Applied MAVLink receive thread stack size adjustment, and excluded UAVCAN, uXRCE-DDS, mag bias estimator, and SIH from the default build to free up flash memory for FMUv4 (Pixracer).

This beta release is the final refinement stage for the upcoming v1.18.0 stable version, and extensive testing is crucial to validate its stability and performance. Given the numerous fixes related to new board support and driver updates, developers using relevant hardware are strongly encouraged to conduct thorough testing and provide feedback.

Core GitHub Updates (PX4-Autopilot)

Key Merged Pull Requests

Over the past week, several important PRs across various domains have been merged, enhancing PX4’s functionality and stability. The focus was primarily on driver stabilization, internal system optimization, and improvements to the simulation environment.

• fix(drivers/bmp388): poll STATUS without consuming the data registers: Improved data collection logic for the BMP388 barometer driver, enhancing stability.
• feat(sim): add RotorPy simulator support: Added support for the new RotorPy simulator, expanding the simulation environment. This will contribute to testing various flight models and scenarios.
• fix(simulation): align gz_x500 rotor geometry with model: Improved simulation accuracy by correcting rotor geometry alignment for the Gazebo X500 model.
• fix(msp_osd): fix OSD_SYMBOLS parameter bitmask behavior and missing elements: Fixed MSP OSD parameter bitmask behavior and missing elements.
• fix(drivers/iis2mdc): read the temperature registers in their own transfer: Corrected the logic for reading temperature registers in the IIS2MDC magnetometer driver.
• fix(nuttx): provide floating and wide abs() overloads on NuttX targets: Improved build compatibility by providing floating and wide abs() overloads on NuttX targets.
• Fix SIH position jumping in 0.7 m steps on real flight controllers: Fixed the Software In the Loop (SIH) simulation position jumping bug, improving operation accuracy on real flight controllers.
• fix(drivers/bmp388): collect after forced conversion completes, rewrite driver 및 fix(drivers/bmp388): wait for cmd_rdy before soft reset: Overall stability and data collection logic improvements for the BMP388 driver.
• refactor(parameters): merge Param<> constructor calls to save flash 및 refactor(platform): out-line ModuleParams setParent and destructor to save flash: Refactoring related to parameters and platform to save flash memory.
• feat(uavcan): configureable max rates for ESC/Servo output: Added configurable max rates for UAVCAN ESC/servo output.
• fix(flight_mode_manager): re-seed trajectory to measured state while emergency braking: Enhanced flight mode management stability by re-seeding the trajectory to the measured state during emergency braking.
• feat(failure_injection): make SYS_FAIL_RC_INST a bitmask for instance selection: Added a bitmask for instance selection to the system failure injection feature.
• feat(failure_injection): add ADS-B traffic failure injection and battery severity levels: Expanded test coverage by adding ADS-B traffic and battery severity level injection capabilities.
• fix(logging/fuelt_tank_status): log all instances of fuel_tank_status: Fixed logging bug for multiple fuel tank status instances.
• feat(fueltank): multi-fueltank_status support: Added support for multi-fueltank_status.
• feat(driver/dlvr): add support for dlvr airspeed-sensors: Added DLVR airspeed sensor driver.
• fix(boards/px4_fmu-v6xrt): fill FRAM with 0xFF on erase 및 fix(px4/fmu-v6xrt): give LPUART1/8/11 a 600-byte RX buffer: Modified FRAM initialization and UART RX buffer settings for PX4_FMU-v6XRT boards.
• feat(vtx): Separate device and protocol parameters for vtx driver: Separated device and protocol parameters for the VTX driver.
• fix(estimator-checks): do not report sensor failure on jamming detection: Modified estimator check logic to not report sensor failure on jamming detection.
• fix(drivers/icm45686): retry WHO_AM_I on probe: Added WHO_AM_I retry logic during ICM45686 driver probe.
• refactor(gps): shrink the GPS driver by ~4 KB of flash: Refactoring to save ~4 KB of flash memory for the GPS driver.
• fix(nxp/adc): initialise each ADC once, not once globally: Corrected NXP ADC initialization logic.
• fix(manifest): return the matching PAB manifest entry: Fixed manifest bug.
• fix(commander): report the worst IMU in the consistency check: Improved IMU consistency check logic in Commander.
• fix(drivers/power_monitor): reject out-of-range INA226 cal and INA228 index 및 fix(drivers/iis2mdc): print the I2C address the driver actually uses: Bug fixes for power monitor and IIS2MDC drivers.
• ci(build-all): install only what the matrix generator needs 및 ci(macos): key ccache per matrix OS: CI/CD optimizations.
• fix(boards/corvon): unquote BOARD_UAVCAN_INTERFACES: Fixed Corvon board build system bug.
• feat(boards/modalai/voxl2): enable temperature compensation: Added temperature compensation feature for ModalAI VOXL2 boards.
• feat(ver): add command to compare population option: Improved version check command.

Deep Dive into Key Open Pull Requests and Issues

Among the unmerged PRs and open issues, significant discussions are underway that offer insights into the future direction of PX4.

Key Open PRs:

• feat(boards): add the ARK FMU-v6XRT, feat(boards): add DAKEFPV H743, H743 Pro and H743 Slim flight controllers, feat(boards/agam-robotics): add Agam Robotics FMU-v6XRT board support: Active efforts are underway to add support for new flight control boards from ARK, DAKEFPV, and Agam Robotics. This is crucial work that continuously strengthens the hardware extensibility of the PX4 ecosystem.
• feat(drivers/imu/st/lsm6dsv): LSM6DSV 80X and 320X, feat(drivers/imu/invensense/iim20670): add the IIM-20670 driver, feat(driver): Murata/SCH16T-K10 IMU with external FIFO driver: Work is ongoing to add various new IMU sensor drivers, which will contribute to improving drone sensor accuracy and compatibility. Notably, the Murata/SCH16T-K10 driver is labeled risk:safety-critical, requiring careful review.
• feat(uavcan): add bidirectional ESC support for uavcan: UAVCAN bidirectional ESC support is a significant feature that could greatly impact power efficiency and motor control feedback.
• feat(gps): Galileo HAS mode, correction protocol reporting, GPSDrivers bump: Support for Galileo HAS mode and GPS driver updates will contribute to improved precise GPS performance.
• refactor(ekf2): separate GNSS heading from position into independent topic: This refactoring to separate GNSS heading information from position data into an independent topic in EKF2 is important for increasing the estimator’s modularity and flexibility.
• feat(navigator): mission route planning library: The addition of a mission route planning library is foundational work essential for advancing autonomous flight capabilities.
• feat(fw_mode_manager): parachute landing via flight termination: The parachute landing function upon flight termination for fixed-wing drones is an important safety feature.
• feat(platforms): upgrade NuttX to 12.12.0: This substantial PR to upgrade the NuttX OS to 12.12.0 is a critical task that modifies the fundamental platform. It’s actively discussed with 68 comments and is labeled risk:safety-critical, requiring in-depth verification. This will significantly impact PX4’s future performance, stability, and support for new hardware.
• feat(SIH): Added optical flow sensor: Adding optical flow sensor support to SIH simulation will enhance testing capabilities for indoor flight and GPS-denied environments.

Key Open Critical Issues:

This week, several critical issues related to security and data processing have been raised.

• MAVLink FTP (NuttX): write-protection whitelist can be bypassed with an Open+List+Write sequence: A severe security vulnerability where the MAVLink FTP write-protection whitelist can be bypassed through a specific Open+List+Write sequence. This implies potential unauthorized access to firmware and configurations.
• GPS NMEA GSV parser: unclamped satellite count causes stack/heap out-of-bounds writes (single sentence crashes px4): Potential stack/heap out-of-bounds writes due to an unclamped satellite count in the GPS NMEA GSV parser. This is highly critical as even a single sentence can crash PX4.
• MAVLink FTP: resend path serializes a 19-byte cached reply as a 254-byte struct (heap out-of-bounds read): An error where the MAVLink FTP resend path attempts to read out-of-bounds from the heap by serializing a 19-byte cached reply as a 254-byte struct. This could lead to data corruption or system instability.
• [Bug] USB MAVLink dies permanently after the host closes the port (Linux USB autosuspend + CONFIG_SERIAL_REMOVABLE): A bug where the USB MAVLink connection permanently dies after the host closes the port in a Linux environment. This issue can frequently occur in development and testing environments.
• cuav/fmu-v6x (v1.17.0): fixed-wing longitudinal control missing — board still uses FW_POS_CONTROL instead of FW_LATERAL_LONGITUDINAL_CONTROL + FW_MODE_MANAGER: A bug where fixed-wing longitudinal control is missing on CUAV FMU-v6X boards. This directly impacts flight stability on specific boards.

These MAVLink-related security and data processing issues directly affect the core stability and reliability of the PX4 system, suggesting the need for prompt action from the development team. The GPS NMEA parser error, in particular, could cause system crashes and should be addressed with the highest priority.

Weekly Dev Call & Community Trends

The PX4 Weekly Developer Call (PX4 Dev Call: Aug 19, 2026 (Team sync, and Community Q&A)), held on August 19, 2026, featured active team synchronization and a community Q&A session. It is anticipated that in-depth discussions took place regarding key PRs and issues currently being debated on GitHub. Sharing progress on critical matters such as MAVLink security issues and the NuttX upgrade would have been particularly important.

The following key trends were observed on the official PX4 Autopilot Discourse forum:

• Firmware and Hardware Connection Issues: Holybro Mosaic-H connection issue and How to connect the DJI Air Unit to PX4 questions were posted. This indicates that compatibility issues arising from new hardware integration and firmware upgrades are significant concerns for users.
• Sensor Performance and Data Analysis: Here4 GPS severe dropout, why? (6 replies, 88 views) expresses concerns about GPS reception stability. This connects with the Galileo HAS mode support PR on GitHub and EKF2’s GNSS-related refactoring, suggesting a continuous need for improvement in precise position estimation and sensor fusion. Discussions on analyzing public log data reflect developers’ efforts to utilize real flight data for system performance improvement.
• QGC Actuator Testing: Unable to test actuators in QGC (3 replies, 49 views) shows that the functionality and usability of ground control software also remain important considerations.

Subsystem Trends (MAVLink, MAVSDK, QGC)

MAVLink Trends

MAVLink plays a pivotal role in communication between PX4, ground control stations, and peripherals. Recent security vulnerabilities related to MAVLink FTP discovered in the GitHub issues section (write-protection bypass, heap out-of-bounds read) underscore the urgent need for enhanced security in this subsystem. Additionally, the stack/heap overflow issue in the GPS NMEA parser (stack/heap out-of-bounds writes) is a significant problem that could impact the stability of MAVLink message processing. These issues highlight the demand for increased community attention and effort in MAVLink protocol implementation and vulnerability analysis.

MAVSDK Trends

No direct GitHub PRs or Discourse discussions related to MAVSDK were observed in the provided data for the past week. However, efforts to update and strengthen the MAVLink protocol indirectly influence MAVSDK development, and related updates can be anticipated in future MAVSDK releases.

QGroundControl (QGC) Trends

QGroundControl is essential ground control software for configuring, planning flights, and monitoring PX4 drones. Last week, two significant QGC-related announcements were made on the Discourse forum:

• QGroundControl v5.1 Stable is available! (31 views): The v5.1 stable version of QGC has been released. This provides users with enhanced stability and new features, marking an important milestone in improving the completeness of the PX4 ecosystem. Users can expect a more stable drone operation experience with this version.
• QGroundControl PR: Add AMOVLAB FlyCore firmware upgrade support (30 views): Support for AMOVLAB FlyCore firmware upgrade will be added to QGC. This demonstrates QGC’s continuous efforts to expand support for various PX4-based hardware and firmware.
• Meanwhile, user reports like “Unable to test actuators in QGC” serve as a reminder that improving QGC’s user experience remains crucial.