CVE-2026-118493: Apache Iggy: Log snapshot exposes the generated root password

Published Nov 18, 2026
·
Updated

Insertion of Sensitive Information into Log File vulnerability in the Apache Iggy server. If Apache Iggy 0.9.0 started without IGGYROOTUSERNAME and IGGYROOTPASSWORD, it generated a root password and wrote it to the server log file, which is enabled by default. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) let a user with only the readservers permission download the server log files. That user could read the generated root password and log in as root.

This issue affects Apache Iggy: 0.9.0.

Users are recommended to upgrade to version 0.10.0, which fixes the issue. Version 0.10.0 never generates a root password, and the snapshot requires the manageservers permission. If a 0.9.0 server generated its root password, change that password.

Affected Software

1 affected component
Apache Iggy=0.9.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Iggy to a version that resolves this vulnerability.

    Fixed in 0.10.0
  2. Operational

    If an Apache Iggy 0.9.0 server generated its root password, change that password.

Event History

Nov 18, 2026
CVE Published
via MITRE·11:54 AM
Data Sourced
via MITRE·11:54 AM
DescriptionWeakness
Data Sourced
via NVD·12:17 PM
DescriptionWeakness

Frequently Asked Questions

1

Who can exploit this issue?

A user who has the read_servers permission can exploit it if the Apache Iggy 0.9.0 server started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD and therefore generated a root password. The user can retrieve log files through a system snapshot and read that password.

2

Are default deployments affected?

The server log is enabled by default. Affected exposure occurs when Apache Iggy 0.9.0 is started without both IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, causing it to generate and log a root password.

3

What can be done if upgrading is not immediately possible?

If the 0.9.0 server generated its root password, change that password. Restricting access to users with the read_servers permission also limits who can download snapshots containing the logs.

4

How can I determine whether a server may already be affected?

Check whether the server is Apache Iggy 0.9.0 and was started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD. If so, it generated a root password that was written to the server log and may have been accessible through the snapshot command to read_servers users.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203