Vulnerability/
https://seclists.org/oss-sec/2026/q4/292

https://seclists.org/oss-sec/2026/q4/292: CVE-2026-59229: Apache IoTDB: Legacy Pipe Privilege Escalation

Q: Which accounts should be prioritized when assessing exposure?

Prioritize users with SYSTEM-level privileges such as USE_PIPE or MAINTAIN, including accounts that do not have WRITE_DATA or DELETE_DATA permission on the target databases. These privileges can be sufficient to trigger operations through the Legacy Pipe API.

Q: Does an attacker need existing write or delete access to the target database?

No. The issue allows specially crafted PipeData messages to cause data loading or deletion as the hardcoded root identity, bypassing the target database's WRITE_DATA and DELETE_DATA permission checks.

Q: What is the available remediation?

Upgrade Apache IoTDB to version 2.0.11. The issue affects versions from 2.0.0 before 2.0.11.

Published Oct 21, 2026

Updated

Affected Software

1 affected component

Apache IoTDB>=2.0.0<2.0.11

Frequently Asked Questions

Which accounts should be prioritized when assessing exposure?

Prioritize users with SYSTEM-level privileges such as USE_PIPE or MAINTAIN, including accounts that do not have WRITE_DATA or DELETE_DATA permission on the target databases. These privileges can be sufficient to trigger operations through the Legacy Pipe API.

Does an attacker need existing write or delete access to the target database?

No. The issue allows specially crafted PipeData messages to cause data loading or deletion as the hardcoded root identity, bypassing the target database's WRITE_DATA and DELETE_DATA permission checks.

What is the available remediation?

Upgrade Apache IoTDB to version 2.0.11. The issue affects versions from 2.0.0 before 2.0.11.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.