CVE-2026-110513

Apache Iggy: Deleted user's HTTP token authenticates as the account that reuses its user ID

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Apache Iggy’s HTTP transport uses JSON Web Tokens that identify users only by a numeric user ID. When an administrator deletes a user, the numeric ID becomes available. If that user’s token remains unexpired or is refreshed before the ID is reassigned, the token authenticates as the next account created with the same ID, granting the attacker that account’s permissions. The flaw effectively allows an attacker to hijack authentication tokens and gain unauthorized access to another user’s account.

Affected Systems

Apache Iggy servers running version 0.9.0 or earlier and deploying the HTTP transport are affected. Only deployments with HTTP enabled are vulnerable. Versions through 0.9.0 are impacted; upgrading to 0.10.0 removes the issue.

Risk and Exploitability

The vulnerability enables an attacker to acquire the privileges of any user whose ID is reused, effectively performing account takeover. No EPSS score is available, but the lack of a KEV listing does not diminish the potential impact; the CVSS score is not supplied, yet the severity is inherently high due to the authentication bypass. The attack vector is the publicly accessible HTTP interface, implying that an adversary with network access to the service can exploit the flaw by presenting a valid, stale token or by refreshing it before the ID is reallocated. Overall, exploitation is straightforward in environments where user deletion and creation occur frequently.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Apache Iggy to version 0.10.0 or later, which removes the token‑reuse flaw.
  • If an immediate upgrade is not possible, disable or restrict the HTTP transport to limit access to trusted networks only.
  • Configure auditing to detect deleted users while active tokens exist, and consider implementing manual token revocation or periodic token expiration to prevent stale tokens from persisting after user deletion.

Generated by OpenCVE AI on November 18, 2026 at 13:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache
Apache iggy
Vendors & Products Apache
Apache iggy
Type Values Removed Values Added
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.
Title Apache Iggy: Deleted user's HTTP token authenticates as the account that reuses its user ID
Weaknesses CWE-613
References
Weaknesses
  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 18, 2026, 11:57 AM
Reserved
Oct 14, 2026, 11:37 AM
Status
Received
Published
Nov 18, 2026, 10:16 AM
Modified
Nov 18, 2026, 12:17 PM