Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.8
CVE-2026-110513: Apache Iggy token from deleted account logs in as another
CVE-2026-110513 · published 4 days ago
Summary
If you run Apache Iggy with its web interface turned on, a user who has been removed can still have a valid login token. When a new user is created and receives the same numeric ID, that old token can be used to access the new account with its permissions. Upgrade to Apache Iggy version 0.10.0 to fix the problem.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| apache software foundation | apache iggy | <= 0.9.0 |
Original advisory text
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.
This issue affects Apache Iggy: through 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
References
- https://lists.apache.org/thread/4gz17yzdz1751fdszhl76fp9or5l1t6v Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/11/17/29 URL
- https://github.com/apache/iggy/pull/4550 Patch
- https://hub.docker.com URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/110xxx/CVE-2026-1105... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-110513 Vendor Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.8
Critical
Type
CWE-613Insufficient Session Expiration
Timeline
Published18 Nov 2026
Updated22 Nov 2026
First seen18 Nov 2026
Track software like this
Free during beta