Apache Iggy 0.10.0 Removes Generated Root-Password Exposure

P2 — VALIDATE AND UPDATEModerate · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Upgrade affected Iggy servers to 0.10.0, change generated root passwords, and review access to logs and diagnostic snapshots.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Iggy versions, startup credential configuration, log destinations, snapshot access and assignments of read_servers and manage_servers permissions. The described exposure requires a 0.9.0 server that generated its root password. Snapshot retrieval required read_servers permission; this is not an unauthenticated disclosure claim. Apply Iggy 0.10.0 and configure credentials using the supported deployment guidance. Change any root password generated by the affected server, coordinating dependent consumers. Confirm snapshot authorization and successful application access after credential rotation. Review snapshot and log access and retain relevant logs, role assignments and change evidence securely.

Open the authoritative advisory

Last verified: 2026-11-18 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeApache Iggy server
AdvisoryCVE-2026-118493
CVECVE-2026-118493
Authoritative release date2026-11-18T11:05:01Z — timestamp of Apache’s original project announcement.
Authority revision dateNo separate material revision is established for this release.
Affected versionsApache Iggy 0.9.0 when started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, causing a root password to be generated and written to the enabled server log.
Fixed versionApache Iggy 0.10.0; change any root password generated by an affected 0.9.0 server.
CVSS base scoreNot provided by the authority
CVSS severityModerate
Exploitation statusApache does not confirm exploitation of this vulnerability in the cited announcement.; no exploitation claim is inferred.

What Changed

Apache disclosed that a user with read_servers permission could obtain a diagnostic snapshot containing the generated root password. Version 0.10.0 stops generating the password and requires manage_servers permission for snapshots.

What To Validate Now

  1. Inventory. Record Iggy versions, startup credential configuration, log destinations, snapshot access and assignments of read_servers and manage_servers permissions.
  2. Establish applicability. The described exposure requires a 0.9.0 server that generated its root password. Snapshot retrieval required read_servers permission; this is not an unauthenticated disclosure claim.
  3. Remediate. Apply Iggy 0.10.0 and configure credentials using the supported deployment guidance. Change any root password generated by the affected server, coordinating dependent consumers.
  4. Validate. Confirm snapshot authorization and successful application access after credential rotation. Review snapshot and log access and retain relevant logs, role assignments and change evidence securely.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Updating the software does not invalidate a password already disclosed in a log or downloaded snapshot. Preserve investigative copies under restricted access before handling sensitive historical logs.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.