Apache Iggy Server Logs Sensitive Root Password Vulnerability
Is it fixed? Not yet.
Ongoing since Nov 18, 12:17 UTC. First reported Nov 18, 12:17 UTC.
What happened
The Apache Iggy server leaks a generated root password into the server log file when started without explicit root credentials in version 0.9.0. Users with read_servers permission can exploit the system snapshot command to download the logs and read the credentials.
What caused it?
If Apache Iggy 0.9.0 is started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, it generates a root password and writes it to the server log file, which is accessible via the system snapshot command by users with read_servers permission.
Source: tenable.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
Apache Iggy server.: CVE-2026-118493 (High)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportApache Iggy server.: CVE-2026-118493 (High)(opens security advisory in a new tab)
High severity. Insertion of Sensitive Information into Log File vulnerability in the Apache Iggy server. If Apache Iggy 0.9.0 started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, 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 read_servers permission download the server log files. That user could read the generated root…
by Tenable 0upvotes 0comments
FAQ
What happened in the Apache issue?
The Apache Iggy server leaks a generated root password into the server log file when started without explicit root credentials in version 0.9.0. Users with read_servers permission can exploit the system snapshot command to download the logs and read the credentials.
What is affected by the Apache issue?
Apache (versions: 0.9.0).
When did the Apache issue start and end?
It started Nov 18, 12:17 UTC and is still ongoing (16 h 26 min so far). This page updates as it develops.
How do I get alerts for Apache?
Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.