Skip to main content
VulnerabilityPublished

CVE-2026-110513: Apache Iggy · DEPRECATED: Insufficient Session Expiration

Affects Apache IggySource CVE Database V5

0
Compare

Not known to be exploited · fixed in 0.10.0 : patch Apache Iggy soon.

Data as of 18 Nov 2026, 10:19 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

Affected software

ProductAffectedFixed in
Apache Software FoundationApache IggyAffected
  • <=0.9.0
Fixed in–
GitHubapache/iggypkg:github/apache/iggyOther threatsAffected
  • <=0.9.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Iggy to version 0.10.0 or later, where this vulnerability is fixed. No other mitigation is indicated. Since this is a session expiration flaw, relying on token expiration and proper user ID management is critical.

Description

Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user's unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account's permissions. Only deployments with HTTP enabled are affected. This issue affects Apache Iggy: through 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue.

References

Community reviews

Loading reviews…