CVE-2026-110513: Apache Iggy: Deleted user's HTTP token authenticates as the account that reuses its user ID
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.10.0
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Only Apache Iggy deployments with the HTTP transport enabled are affected. The issue applies to versions through 0.9.0.
What must happen for an attacker to gain another account's permissions?
An attacker needs an unexpired HTTP JWT belonging to a deleted user. A new user must then be created and assigned that deleted user's numeric ID, after which the old token authenticates as the new account.
Can a deleted user's token remain useful after the account is removed?
Yes. If the token remains unexpired, it can authenticate as the next account that reuses the deleted user's ID. A token refreshed while the ID was free can also produce this outcome.
What is the recommended remediation?
Upgrade Apache Iggy to version 0.10.0, which fixes the issue.