Skip to main content
VulnerabilityPublished

CVE-2026-118493: Apache Iggy · Sensitive Data in Logs

Affects Apache IggySource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 0.10.0 soon.

Data as of 18 Nov 2026, 12:07 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 0.10.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Apache Iggy to 0.10.0.

Affected software

ProductAffectedFixed in
Apache Iggyapache/iggyAffected
  • >=0.9.0 <0.10.0
Fixed in
  • 0.10.0

AI-suggested

Upgrade Apache Iggy to version 0.10.0 or later, which fixes the issue by not generating a root password and restricting snapshot access to users with manage_servers permission. If running version 0.9.0, change any generated root password immediately.

Description

Apache Iggy version 0.9.0 has a vulnerability where it generates a root password if started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, writing this password to the server log file. Users with read_servers permission can retrieve the server logs via the snapshot command and obtain the root password, allowing unauthorized root access. This issue is fixed in version 0.10.0, which does not generate a root password and restricts snapshot access to users with manage_servers permission.

References

Community reviews

Loading reviews…