Skip to main content
Menu
CVEs

CVE

Apache Iggy root password exposure in snapshot logs

CVE-2026-118493Published Updated Summary written by a model

Exploited
No known exploitation
Fix
Fixed in 0.10.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.10.0.

Summary

Apache Iggy, a server product from the Apache Software Foundation, wrote its auto-generated root password to a log file that the snapshot command exposed to users holding only the read_servers permission. Such a user could download the logs, read the password, and log in as root.

Original description

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 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 manage_servers permission. If a 0.9.0 server generated its root password, change that password.

cve.now Index

0Pcve.now Index 0 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.10.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-118493 (Apache Iggy: Log snapshot exposes the generated root password), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-118493 (entry last updated 2026-11-18):
Affected:
- Apache Software Foundation Apache Iggy: from 0.9.0, fixed in 0.10.0
Fixed versions: 0.10.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-118493 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118493 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/zcdflk6ztljfqgw8tfqvgrg0m9n0bxkk
- https://github.com/apache/iggy/pull/4585
- http://www.openwall.com/lists/oss-security/2026/11/18/5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-118493
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118493"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • apache/iggy

    From 0.9.0 · fixed in 0.10.0

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorylists.apache.org · thread/zcdflk6ztljfqgw8tfqvgrg0m9n0bxkk
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-118493
RecordNVD · CVE-2026-118493
Write-ups 1Establishes: Technical detail and context.
Linkopenwall.com · lists/oss-security/2026/11/18/5
Other links 1
PatchGitHub · apache/iggy · Pull request #4585

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-118493

Is CVE-2026-118493 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-118493?

apache/iggy: from 0.9.0 before 0.10.0.Source: cve.now feed data

How do I fix CVE-2026-118493?

Upgrade to a fixed version: 0.10.0.Source: cve.now feed data

More CVEs